-
Notifications
You must be signed in to change notification settings - Fork 9
Open
Labels
Description
Story
As a tester, I want to run just one method in isolation from within a test class, so that I can just test the one method I've just written, rather than waiting for all the methods to run.
Background
Our legacy testing framework did this, and as such, all our existing unit tests are written in a way that they do not depend on other methods running first.
This allowed testers to run just one method in particularly large test classes, speeding up development time
All the before's & afters would need to still run, but the actual test method list to run would be filtered down to that one single method selected.
CLI changes
galasactl runs submit local --obr obrs --class className --methods method1,method2
galasactl runs submit local --obr obrs --class className --methods method1 --methods method2
Tasks
Framework changes
- Launcher needs to accept both the class and a method name
- TestRunner still needs to parse test class - but when we get the TestMethodRunner, check that the method has the given name and just run that one.
CLI changes
- Implement changes on to runs submit local
- Documentation / Release notes
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
👀 1 In review