Forum Discussion
I am a long time supporter of Smartbear and the SoapUi/Ready!API suite and have personally been the reason for a massive uptake in making use of the licensed product. While this problem is manageable with methods that have been stated above, it results in an extraordinary amount of effort to ensure that there are no faulty or unnecessary updates. In the scenario where I am making valid changes to _specific_ tests this is affecting and touching every other element. Meaning a small update results in a big commit that obfuscates the thing that is being updated.
This is further highlighted as I find our test packs maturing and growing *looks at one example in source tree - 55 Changes*.
I cannot stress how important it is that this issue is focused on and adjusted for composite projects.
Composite project 1.4 anyone?
+1 for Improvement
(P.S. I can't wait for 1.10.0 or 2.0.0 ;D)
Related Content
- 6 years agogenki
- 11 years agoshehbashahab
- 3 years agomgavan