Large test projects may consist out of several thousands of test-cases. Often executing them all would need a considerable amount of time, even if multiple machines are used in order to replay the different tests. The solution are tags.
Continuous Integration Systems (CI-Systems) support the teams at their steady work on the various sub-steps of the software development process. The main objective being the improvement of software quality.
There‘s no way around using variables if a test-suite has to to be flexible, reusable, and elegant. But where are variables set? Which value of the variable is used if I defined multiple ones at different positions? And how can I find out? This article aims to answer these questions.
You are working with QF-Test and something something doesn't work as expected? Then you can (as usually) search the Internet or do research at Stackoverflow... A faster way is going on our channels ...
Some days ago I had the pleasure to visit a Meetup Venue here in Leipzig, Germany. The topic was very interesting - "Experience with the introduction of Test Automation". Many of the participants consider Web GUI Testing very fragile and cumbersome to keep in "Tests OK" status that's why I I decided to write this series with the topic: No coordinates based Events and no Image based checks! QF-Test is smarter than that!
In order to simplify test-suite editing it is possible to assign colored marks to nodes. This feature is especially (but not only) helpful in the context of complex find and replace operations - in this case, the color markers can for example be used to indicate that a node still needs revision or that a node was edited successfully.
Nous utilisons des cookies "Matomo" pour l'évaluation anonyme de votre visite à note page web. Pour cela nous avons besoin de votre consentement qui est valable pour douze mois. La révocation est possbile n'importe quand sur notre page "Protection de données".