You are working with QF-Test and 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.
QF-Test uses semi hard events as default (based on web ajax toolkit, browser and browser version, OS etc), but not all cases. There are three event types available.
Indeed, it is quite confusing if you would take a look how the supposed license files attached to emails are arriving. Although it is actually quite simple …
QFS (Quality First Software GmbH) is one of the best employers of the ITC industry in Germany and also in Bavaria. We are located in Leipzig and in Geretsried (that’s between Munich and the Alps at the Isar river) and have won the Great Place to Work award already two times now.
In most cases we are dealing with more or less straight-forward GUI components,such as buttons and text fields. Nevertheless we often have to deal with morecomplex GUI components like trees, tables and lists too. These GUI components have sub-items.
Sensitive information like passwords should be treated with care. However often tests need to fill out a login form and thus these tests require to know the password.
