Support #7342
evolve testcases project configuration and scripting to simplify, standardize and automate setup
0%
History
#1 Updated by Greg Shah 12 months ago
The Testcases project has been quite haphazard in our setup and configuration. We've never properly or consistently defined the project for general use. Instead, each person working with it has left their own changes behind, doing just enough to get themselves past whatever short term need they had.
We are implementing CI/CD to run these testcases on an automated basis. This means we really need to clean this up now. Some immediate questions:
1. How do we manage the directory? Do we implement one for each test suite (meaning that each test suite has its own FWD server)? This has the advantage of making each test suite's configuration easier to understand. It has the disadvantage of creating a large number of parallel configurations that will be more work to manage over time.
2. How do we handle database usage? Do we implement a different database for each test suite? Or do we merge everything into a single database?
In addition to figuring out the above, we need to extend our scripting/standard project support/tools as needed to cover the full range of needs for this project. I would expect any solution here will be something needed in other customer projects, so we don't want one-off solutions.