| || |
UFT for Test Driven Development. Will it work?
Are there any real disadvantages with using UFT/QTP in a Test Driven Development environment? Are there better tools to use in this environment?
It's do able. TDD is really a process and is tool agnostic. But given UFT/QTP generally does not have deep hook into the SUT's internals. You'll be closer to the realm of ATDD (Acceptance Tests Driven Development) You won't get the same milage as using the same language as the development, but it is still a good development practice.
Originally Posted by PeterKlim
The same principals apply. You'll first write a failing test, but because the SUT does not have the features yet, you'll write your tests and document the ID/locators used and give that to the developers to use.
Generally I would just do TDD tests in the same language as the developers and include it in the SUT source code under a separate /requirements directory for requirements using BDD/Gherkin syntax, and the backing tests under the /tests directory. This makes the project it self a source of living documentation.