Forum Discussion
10 mb is a big size project.
Hope support team comes up with their findings and possible solution.
By the way, how important is to change the order of suites?
Hi,
"10 mb is a big size project." --> according my evaluation, we coded only about 10% of what we need to cover... So, your remark makes me afraid (!)
"how important is to change the order of suites?" --> the order is important in two way:
- for a readibility criterion (the way we order the suite makes sense)
- for a Run point of view: we need to run SuiteX before SuiteY and SuiteZ as X prepares data for the two others (for instance), or we would like to run first the Sanity Suites, just to be sure all is OK at the first minutes
- nmrao4 years agoCommunity Hero1. Split the project if it is going to be big.
2. Each test should be independent.- _Oliver_4 years agoContributor
I had a similar issue two times in the past. I remember I had some properties transfer that were not properly defined (when cloning of other test suites, I had warning messages about that and I ignored them). I can't tell for sure that it is related but both times, after correcting the property transfers, the freezing stopped.
There does not seem to be any obvious link between a "non-properly defined" property and a freeze when moving a test suite but I thought I would mention it anyway, maybe it can help.