Forum Discussion
Marsha_R Of course, it all depends the internal (within the business/organization) processes and procedures about what and when is communicated, along with the chosen software development approach (Agile, waterfall, incremental, hybrid).
That's why it should be configurable (let TC do changes automatically/suggest changes but let tester decide/do "nothing"), in TC's general settings.
Working in agile doesn't prevent the testers from knowing what they have to test... if you don't know what is new, there is probably something wrong in your processes
- Marsha_R8 years agoChampion Level 3
Yes, Montikore That's exactly why I don't want TestComplete changing the name mapping without me knowing there was something wrong. Occasionally there are changes made to our part of the code base by another team and we aren't informed. I want my test to break so I see the change. It's a quick fix and I can also remind the other groups to share the information. It's a test for our processes as well as the code.
- mgroen28 years agoSuper Contributor
Marsha_R, Montikore It all depends on the environment (type of business, choosen approach for software development).
For example in Agile/CI and other short approaches with short development cycles the focus is primary on delivering working software, meeting customers requirements.
In such environments there is not always time to evaluate consequences of changes influencing other teams!
That's why the automation tools need to become better (more intelligent) in handling changes.
I would love to see TC handle name mapping changes automatically so I can focus on changes on higher level op abstraction in the short time I have for next delivery of the software!
- Marsha_R8 years agoChampion Level 3
For another example, we have been using Agile for several years and we don't have a problem updating our tests if an issue is found.
- mgroen28 years agoSuper Contributor
Marsha_R Agile is a broad term and can be implemented in multiple forms and flavours, and degrees and in more/less delivery speed/frequency.
Some people say "we use agile" but in fact just use the name and really do not make fast deliveries of their software!
My point is: Smartbear (TestComplete) should be upgraded to support CI / CD and BDD processes, otherwise it will lose it popularity and marketshare. Times are changing and SmartBear has to "make the shift"!
- Marsha_R8 years agoChampion Level 3
And testing is a broad term and can be implemented in multiple ways. Some people say "we know the best way" and really all they know is their own situation.
My point is that TestComplete is a good generic tool now and what SmartBear should do is what they think is best to improve it.
- mgroen28 years agoSuper Contributor
Marsha_R Of course it's up to SmartBear internal teams/ product owner to decide in what ways to evolve the product(s).
But we, testers, QA-engineers, developers, test managers, etc, are the eyes and ears of the product. We know best what is happening in daily work environments. And that's why we need to discuss things on forums. Eventually SmartBear picks up these signals and do with it they think is best for product evolution!
Related Content
Recent Discussions
- 9 hours agoSubhraDas