It’s an architecture as per @angus’ diagram, with multiple repos involved, but this is the status server:
https://github.com/paviliondev/discourse-plugin-manager
It’s also an approach:
- Never implement a fix without checking for a test, and if a suitable test doesn’t exist, add one.
- Preferably develop the test first, show that it fails, then fix the problem and confirm your new test passes.
That way your coverage builds over time …
Moreover:
- Retrofitting tests can be risky as you might misinterpret what the code intended to do … better than doing nothing though …