interviews

How would you present STAMP? 

Writing rich test suites able to bring a high level of confidence in your software is a costly and time-consuming endeavour. STAMP takes your existing tests and automatically amplify them, to generate more tests, increasing test coverage and reducing the number of regressions.

How would you present STAMP? 

From my point of view STAMP is some kind of augmented reality to the service of software testing design: when I, as a developer, design test cases and test configurations for my software, STAMP helps me to enhance my design with several variants, also assessing how good are my test design.

How would you present STAMP? 

STAMP aims at improving the Software Engineering QA process in a 3-dimensional approach that largely improves the efficiency of the design, implementation and execution of test cases on a SUT (System under test) over multiple configurations.

How would you present STAMP? 

The main goal of STAMP is to automatically generate tests from existing assets (scenarios, configurations and logs), to detect regressions and reduce tests cost.
Writing and maintaining test suites manually are costly or … not done !

How would you present STAMP? 

STAMP addresses the need for increased quality of automatic testing in a continuous delivery pipeline. Companies that have adopted DevOps already have a culture of automatic testing, but also acknowledge that the quality of their test suites can be improved.