Spontaneous cleaning out of source test suite project
All best wishes for 2021.
For quite some time we have issues with the SOAtest project (running version 9.10.8) that is contaning the source test suites. From time to time this 'library'project gets cleaned out with an irregular interval.
Currently this source project contains about 100 test suites (and is still growing!). In the same workspace we have 'runnable' projects that make references to the source test suites (and have dedicated data sources). This way we can run the test suites in a desired sequence in order to automatically test the database and validate output files etc. Once the source tst is gone, all references to it are disabled.
I thought this is a straightforward setup and the way Parasoft SOAtest is designed to be used. However, maybe there is a limit on the number of test suites that can be hold in a single project or this can be configured somehow or oherwise there might be a (memory?) problem in SOAtest holding that many test suites altogether in one project.
We can eventually rebuild our framework using the latest remote pushed version from GIT in a brand new workspace. A simple pull of fetch sadly does not yield any retrieval, since GIT 'thinks' all is still right.
So, to cut things short: Is this cleaning out of a project a 'common' feature and should we restrict to a max number of tst's or is this a bug in SOAtest. Are there any other (external) factors that we should take into account (e.g. operation system, platform)? WIll this feature be fixed in a future release of SOAtest?
Thanks in advance for your thoughts.