user interface - Automated GUI Testing: Meeting Us Halfway -
I have been working to develop a system for automatic GUI testing and I can use some advice for luck In the form, we are in the midst of a major redesign of our GUIs and working developers are open to make their code more optimized for automation. My problem is that I'm not sure what to add them. Any hooks that have been added can not affect the functionality, presence or security of the interface and there should be no noticeable effect on the display. In addition, the sky is the limit!
Application in question is a web based Java application that is accessed by AJAX. Most of the existing features are coded using JSP, Javascript and a little Flash 8. Will be done using the next wave of features. I have settled too much as a testing tool due to the flexibility and price tag (free). Key point: I am making a target for testing-reusable and easy maintenance.
Does anyone provide directions that a hook can be placed in it, can provide guidance about it. Do code or some best practices make test development easier and make yourself stronger? Basic Guide Principle: If they want you to test something, testers need a way to get an application in that situation, And once in that situation, it is a way of validating that the state is right.
So the first thing to do is to ensure that they understand that the automation is programming and the UI is your API.
-
Do not change the agreement arbitrarily in the UI - If tester Bob sees that the component has changed from one button to a link, and this device matches the click and runs goes. While a relatively easy code change in automation, this is a change that can be done in many places. (As a tester your job is to understand that there is a change and reduces the cost of maintenance; their work is only to make significant changes and to understand the effect)
- < P> Determine what page you are on .... Bob can tell the difference between login and entry, but how will the automation know? If a login area with the 'username' label, login page If the order number, an entry field with the order field
-
Ask
-
Ability to dump the program status
-
Constant error handling & amp; Reporting (also just good UI design)
< / Li>
A method of identifying each element that you need to interact with (click, type, verify, etc.) and not INPUT_42 ....
Comments
Post a Comment