InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

A new Method for Web Testing assistance

IP.com Disclosure Number: IPCOM000237864D
Publication Date: 2014-Jul-17
Document File: 8 page(s) / 219K

Publishing Venue

The IP.com Prior Art Database


As Web2.0 app becomes more and more popular nowadays, the testing work of web2.0 app is also becoming more and more important, the traditional way of testing, both manual and automation will be not well enough for complex web2.0 app. manual testing cost effort, and automation can not well cover all the issues, especially for the UI part of a complex web2.0 issues, use these two testing methods separately is not a good enough solution for complex web2.0 app. So this article describes a new way of testing, which combine the manual and automation way together inside one test case, so as in order to make a completed solution for complex web2.0 app, expecially the testing of the UI part.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 8

A new Method for Web Testing assistance

When we are testing web applications, we can process our testing phase in two ways: one is manually by tester, another is automation testing. But nowadays, especially in UI testing, we are facing a more complex issue: In one test case, some of the step can be processed automatically, but some steps still need to be verified manually like UI testing.

There are some known solutions, but each one is having its own drawbacks.

1. Test all the cases manually.

2. Make a more complex automation test script for the cases.

3. Some test case(API primary) are processed automatically, some test case(UI primary) are processed manually.

However, all of them have obvious shortages and doesn't well address the challenge:
1. It wastes too much time in steps which can be automated.

2. It is impossible to make a detailed automation script for all the cases, especially for UI testing.(too many properties need to verify which can not be covered perfectly)

3. To judge which one can be processed automatically (not manually) is not convincible. and if case changed, it will take more effort to transform the automated ones into manual ones.

This invention describes a method that will help developers to do automatic tests that needs manual intervention. In general, an automatic test stops when manual operation intervene. Traditional automatic tests do not have the ability to detect manual operation result and compared it with the test case. In our methodology, we will analyze test cases and generate automation steps and manual steps. During the test process, automatic tests and manual tests can be run interchangeably. Compared with other solutions, tests will stop because of manual intervention.

This invention consists of the following steps:

1. Analyze and parse test cases into different steps.

2. Adding functionality of automate running steps forward and backward

3. Wait for user's manual operation and continue the test after the manual operation is done

This invention brings the following benefits:
1. Test case generate test steps automatically
2. Running test forwardly or backwardly.

3. Tester can do manual and automation mixed test without break

1. The overall structure and process


Page 02 of 8

Following is the whole system structure:



Page 03 of 8

2. Case Analysis & Processing


Page 04 of 8

The system reads in the contents of the test case, in which every line indicates a step. The first line in the test case should be the URL of the test page
Every step in the test case should be written in the following format:
[target] [operation]

For example:
some-dom-node click
another-dom-node mouseover