软件测试自动化之路(1)----编码对自动化测试的影响!

 

Author:budapest

                                                                                                 

0. Agenda Dev&TA
1.Testing Automation(TA) in Software testing
2.How to implement a actual testing in Robot?
GUI cases and None-GUI cases
4.What supports is expected from Dev?
5.Common interface

1.Testing Automation(TA) in Software testing
1.1) Manually Testing
1.2) Automatically Testing

2.How to  implement a actual testing in Robot or other tool?
2.1)The Process of Robot implements TA
2.2) Robot’s verification point
 
3.GUI and Non-GUI Case
3.1)Three testing interface of programming
    Command Line
    API
   GUI
3.2)Enlarge mensurability of programming
Some Application under testing(AUT) have one or tow interfaces ,even more. All above interfaces  are  also testing interfaces.
Generally,API and Command Line are more easier than GUI interface to implement  automation testing. Sometimes they are hidden inside the AUT,however if there is no anyone,developers might provide command interface or API interface. As a result,enlarge mensurability of programming.
 Example1: Command line testing interface, such as URLAPI
 3.3)Face GUI testing interface
 Why face GUI ? Since we have used Rational Robot for GUI testing, meanwhile Rational Robot is one of test tools basing on GUI.
 GUI automation testing is a little  difficult:
•Testing script need manually establish.
•Troubles will appear when combine GUI tool with AUT.Such as non-Standard controls or customize controls/owner-draw…(see instance)
•GUI design have changes.
Example2:Standard controls Vs non-standard controls
Example3: keep an identity property for your link/button/…

4.What supports is expected from Dev?
It is time for us to make a conclusion like the topic after we had a long talk:
•Share more Command Line/API interface if you can;
•Consider using standard controls instead of non-standard if standard control have the same competence reaching feature requests;
•Try to keep a identity property for your window/button/list box/link…;
•Avoid  making a large changes in UI after the revise build or 2,3,4…builds if you think TA do regression testing…
If you can’t obey above items,at least please give us a notice when you decide to change your controls’s property,especially  Type/Name/Text …GUI elements.