Search Here:

QA Testing Materials » Basics of Automated Functional Testing

Basics of Automated Functional Testing

Basics of Automated Functional Testing

Now we are going to discuss the basics of Automated Functional Testing.

The general scheme of work

  • Write only pre-planned test.
  • Goals and objectives of the test defined earlier.
  • The chain of operations is clear, the expected results are clear.
  • The possibility of parameterization is determined (which variables can be defined as parameters).
  • Write a script that simulates a complete business process - what we do. If a business process with the ongoing results is carried out in several stages: the script is divided into several Actions (for example login / order / logout).

Obtain a "non-parameterized" script, which can enter what we entered during the recording and did not test.

  • Create CheckPoints (control points) - what we test. Checkpoint can be created in the process of writing the script, and after the debug (if necessary). The second option seems preferable.

Obtain a "non-parameterized" script, which can enter what we entered during recording and check whether it is displays the same thing that he had seen during the recording.

  • Script parameterized (if possible and necessary to have one) to give the script the "volume". Example: declaring a login / password as parameters, we can emulate the script a serial login to the system for so many users, how many values we specify.

Obtain a "parameterized" script, which can enter a set of given values, and repeat as many times as the number of values defined for each parameter.

Posted on 09/06/2011 12:43pm
RU EN

Food for Thought

“If you don’t care about quality, you can meet any other requirement”
(Gerald M. Weinberg)

Our Clients:

Our Clients:

Testimonials:

Knowledge Center

Knowledge Center

Subscribe

*- required fields

Reset all fields