On 1/6/19 11:05 PM, William Brown wrote:
Hi,
When developing I find that I only end up running the basic test + the test
case for the feature or fix that I’m developing. I think it would be good to
have a few more to run as “sanity” tests on our laptops before we do the full
CI. What would be a good range of the suites that we should run on builds
during development?
Good question. I think the answer is really all of them :-) But
seriously this is something we should look into. So we "started"
creating acceptance tests in each test suite, but they are spread out
and not in a generalized location (essentially hard to discover). And
we only have "acceptance" tests in replication, plugins, and GER.
We are also trying to port everything to the suites, and not use
individual ticket tests anymore. This is a long road to getting this
all done, but we should consider expanding the basic suite to include
acceptance tests for all areas (maybe have a script that just points to,
and runs, the other suites' acceptance tests).
Mark
Thanks,
--
Sincerely,
William
_______________________________________________
389-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
_______________________________________________
389-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
