Robot can perform according to the mode of normal development, using the test case to correspond to the test script.
I have not used a fully automated testing process, and I need some test scripts when I need it.
Like my understanding, testing and development, the code should be low coupling, in other words, to do the code only related to the test cases currently testing, without having to have a relationship with other modules, which may involve some problems For example, some front data content call, process cutting, etc.
If it is a script developed by many people, it is quite easy to combine. It may be no problem with it. If you put together, you should consider much, such as the data call, and some interface applications.
Seriously, if a test script does not have to be more than 20 times, don't write, otherwise it will waste time. If there is no test time for a few months, don't put everyone's script to combine test, otherwise I will take a lot of time.
The development of test scripts is actually the same as software development, and thinking about software development in software engineering, you can try to avoid some of the issues in automation development.
I admire some people to say that the test script can run for a few hours, how much test script is written and debug it, and saying that Robot debugging is really bad, it is difficult to check, anyway, I am If you don't write, you will go to write the script only when you involve some of your data entry and cycles.
Automation tests say good, but now the theory and tool support is not too good, I feel that I can cheat outsider, I don't believe it for the time being, most of them, the efficiency and result of manual testing is It is better than automation.
I have a book with Robot test, at home, forget what name, mainly using Robot to establish a test framework, use keyword test methods, have time you can go to the bookstore to find it.
