-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor RegTest tests into package groups #13
Comments
With STO, I'm imagining we could have something like:
As we drill down in to each Spec, we should see reports for each "feature" test and the feature descriptions (Groovy method names with spaces) should be human readable. (We may also want to consider publishing the default Spock test report output if we feel it is more readable or navigable than the standard Jenkins reports. We may also want to look at Jenkins plugins.) |
I really like the report Groovy/Spock creates, and it would be great, if it were exported by default. Even though the STO test plan can be splitted into groups such as "reserved balances" and "transaction ordering", in the end the actual tests are likely the same, but executed on another set of input data. At least that's my impression at the very moment. If we can group it into logical groups, I would really like it though. |
Implemented in commit e2d55a4. |
This Issue assumes that Issue #12 will be completed first, although the same basic reorganization could be done in sub packages of
org.mastercoin
.Currently all the useful Omni Protocol RegTest tests are in the
org.mastercoin.test.rpc
package. I propose a new package hierarchy to improve reporting. Something like:foundation.omni.test.rpc.sto
- Send To Owners testsfoundation.omni.test.rpc.dex
- Distributed Exchange testsfoundation.omni.test.rpc.basic
- basic tests of RPC functionsfoundation.omni.test.rpc.misc
- miscellaneous tests using RPCThis will allow us to view Jenkins reports at the package level and focus on a particular category of tests like "STO".
Currently the test Specs are all lumped together in a single package, generating this report. Adding an extra level of hierarchy here should make things more logical and allow us to write documentation with links to the reports for just one package, such as "STO".
The text was updated successfully, but these errors were encountered: