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.

Via the run-log QF-Test provides a detailed log about the actions it executed during a test run. The overall results of this run-log can be summarized in other reports like the HTML/XML/Junit report.

Even in early stages of development Capture Replay offers. An early start of such regression tests and the assignment of unique names / IDs are the most important bases for efficient (due to stable recognition) test automation.

Sometimes it is needed to perform mathematical calculations in QF-Test, e.g. in order to calculate the expected height of a GUI element in dependence of the complete window size or the exact clicking position for a mouse click.

Software bugs are annoying - for users and software manufacturers alike. The latter, however, should use bugs to continually improve the software, preferably from the beginning of development. Nevertheless, there will probably never really be flawless, right? Rather a philosophical question.