automation development and maintenance by spec

[adrian-herscu]

Hi all,

I am thinking about using such tool for developing and maintaining QA automation projects.

QA automation development is somewhat similar to regular software development in the sense that it uses project management tools, libraries and frameworks, but it differs in two ways:

1. There is no meaning for writing a test for a test, hence no point in mocking external services either.

   (there might be infrastructure code which can be decoupled from external services and tested as unit code)

2. The tests must be somehow related to a feature or usage scenario, and that must be reflected down to actual code.

   In practice, the features, their usage scenarios, and their tests are documented in some ALM. When the automation executes it produces some kind of report. This report might be reflected into the ALM itself or in some dashboard or in a bunch of files. Either way, the produced report must track back to the tests in the ALM.

Anyone tried speckit on such project?

Assuming that tests documented in the ALM are well defined, that is, one can manually execute them without any additional knowledge about the system under test, then how would you close the gap between the ALM and speckit?

Found #730 in relation to last question.