Forum Discussion
I'm with AlexKaras... while there is some part of TestComplete that can help with TDD, I think what you're suggesting might be a bit beyond... definitely look into TestLeft.
As it is, though, you can play the TDD role in an Agile/Scrum/KanBan environment. As you're developing new features of the application under test, you can start building out your regression automation. Having a good framework for doing so will help with that, of course. But you can start writing classes, building out functional routines, etc., based upon the assumptions from the specifications and requirements. That way, when the feature is delivered, you can start plugging it in.... and, if the feature doesn't match what the requirements communicated SAY it should, you can go back to the dev team and say, "Hey... this isn't meeting the documented requirements." Not exactly TDD, but it IS a QA role that automation can fill.
If you do end up using TC tests for developers just to run, then consider giving them TestExecute. They're not going to analyze the test results, they just need to know if it passes/fails.
- AlexKaras8 years ago
Champion Level 2
Well... My initial reply was with assumption that developers will create tests during development and execute them then.
But if the idea is to provide them with already existing tests that developers will just trigger and check their results, this may be a good idea. With the only note that either tests must be extra stable and reliable so that they do not fail because of low performance of the tested application or other false negatives, or, alternatively, someone from test team must provide assistance with test logs analysis to separate false negatives from real failures. And this assistance must not be considered as something that can be done while coffee machine is making another cup of coffee. Usually, such logs analysis is a serious task that requires a reasonable amount of efforts.
- mikakoistinen8 years agoContributor
Hi,
Thanks for Your replies!
I (of cource) forgot to tell about our product.
It a legacy application, part of code base has been written in Turbo Pascal 3.0 , but of course updated. So currently working with Delphi 2007, migrating to D10.1 New functionality is added weekly, sometimes daily.
We do add units tests, but when some part of program is huge case statament, with strictly coupled code, unit testing can be hard. We are working to improving unit test coverage, but it's a long way...
But I'll thing these points and we will make some kind of movement.
thanks again!
- tristaanogre8 years agoEsteemed Contributor
TP 3.0?!?! Really? Back in 1992 I took classes in my under grad for TP 5 and TP 6... wow....