Today we’re pleased to announce an important extension to our automated unit testing tool: the ability to run tests hidden behind namespaces.
The original iteration of the test runner didn’t run tests within namespaces. This was a conscious choice - often these tests are parts of installed packages. Since these packages sometimes contain a huge number of tests, including them by default would introduce problems with noise in your monitoring job’s results, and could also result in the test run taking a very long time to complete.
Having said that, sometimes you do want to run namespaced tests. Gearset will now help you out with this, by allowing you to select exactly which namespaces you want to include in your daily test run.
When setting up or editing a test monitoring job, you’re now able to specify a list of namespaces to run tests in:
Tests which aren’t inside a namespace will still run. If you don’t want any namespaced tests to run, you can leave the field blank and Gearset will exclude them.
When your monitoring job has run, you’ll be able to see the usual breakdown of successes and failures, with an added column to tell you which namespace a test belongs to:
As always, we’d love your feedback on how we can continue to make Gearset even better. You can reach us at [email protected], or through the live chat. You can also add suggestions and comments in our feedback forum.