Codeless Automatic Test Generation with Selenium or UI Automation

The generated tests cover filling in of forms, checking table cell values, checking headings and many more situations.
Just watch test generation in action.

How to Generate Tests for Your Application in Minutes with MyITest4U and Selenium

Test Generators are based on language standards.
They can be used universally and require no maintenance.
Test maintenance boils down to regenerating the tests.
This makes test maintenance very easy and very fast.

Try it Yourself

Get a free Trail

or
Read the Full Story

First

Collect

Collect all GUI elements on a web page automatically.

Do the same for a window in a desktop application.

Why stop there?

MyITest4U will collect all GUI elements of your application automatically.

All you have to do is press start and wait till MyITest4U finishes the job.

One word of warning ...

Warning

Collect

MyITest4U will click every link, button ... on each page.

A lot of work will take some time.

Lucky you MyITest4U is working.

Delete, Sign Out ... are not excluded by default.

Avoid surprises and speed collection up by reading

Configure MyITest4U

Second

Generate

Show all GUI elements on a web page or window ordered by type.

Easily add all GUI elements of a certain kind to a test.

Why stop there?

MyITest4U can generate tests automatically.

Powerful test generators are even build in.

An other word of warning ...

Warning

Generate

The build in Test Generators:

  • need to be configured before use.
  • know nothing about the AUT logic.
  • might contain not working steps.

Configure MyITest4U

Third

Run

Create batch files to run your tests automatically in one go.

No other tool is needed.

No warnings here ...

Fourth

Analysis

 

 


is build in

with powerful features.

 

 

Just have a look.

Curious what Collect, Generate, Run and Analysis is all about?

Give MyITest4U a Try

Want to learn more?
Just keep reading
or
watch:

Test Generation with MyITest4U and Selenium using the structure of the HTML document

Why MyITest4U?

Because MyITest4U:
  • is codeless test automation by design.
  • no need to insert manual timeouts.
  • can generate tests / test templates automatically.
  • Test Generators are build in and easy to use.
  • Test Generators can be customized using the GUI.
    No programming skills are needed.
  • Test Generators are maintenance free.
  • test maintenance is easy and fast.
  • the best possible GUI element locator is always used.
    It is determined at run time using the GUI element attributes.
  • the way the best GUI element locator is found is configurable down to GUI element level.
  • provides "free" universal checkpoints.
  • is modular.
  • collects all GUI elements before using them.
  • stores GUI elements in a data base using an unique identifier.
  • knows all attributes of a GUI element.
  • uses always the same user defined search strategy.
  • separates test logic from your application logic.
  • does everything only once.
  • gives support in test migration.
  • separates test parameters completely from tests.
  • everything has its own place and is done always the same way.
  • has a clear separation between Test Generation, Execution, Analysis and Migration.

FAQ

  • The short answer is: No.
    Even better: It is not possible to program anything as MyITest4U does not have any test scripts.
  • The longer answer is: Fine tuning of MyITest4U for your application might need some programming skills in Java or C#. Once the fine tuning is done you are back to the short answer.
  • The even longer answer is: Programming skills come in handy to replace manual task in test and mainly test data generation.

Confused?

Read MyITest4U explained.

Knowledge of these tools can be help full but it is not required.

Yes of course.

Yes of course.

A Trial says more than a tausend words.

Give MyITest4U a Try

There is more to say.
Just keep reading.

MyITest4U Explained

How do you use a GUI?

  1. Find a GUI element
  2. Do something with the GUI element
  3. Check the result
  4. Go to 1.

The given 4 steps are all you need to do.
Checking is done many times implicitly.

A simple example is using a login form.
A common login form has the following GUI elements:

TextField: UserName
TextField: Password
Button: Login

The login is done by looking for the GUI elements, doing the actions and checks given below:

GUI Element Action Check
UserName: Enter UserName Text can be entered
Password: Enter Password Text can be entered
Login: Click Login button User is logged in

Test Automation can be done in the same way.

Test Automation

A human user uses his eyes and knowledge to find a GUI element.
A Test Automation Tool uses properties of a GUI element to find it.
Examples of GUI element properties are:

  • id
  • name
  • xPath
  • ...

All of these properties are in textual form. This means they can be written down and stored for later use.
Each GUI element has to have an unique set of properties to be found easily.
After a GUI element is found something can be done with it. Possible actions are:

  • click
  • write some text
  • select
  • ...

The coupling of an action to a GUI element results in a test step.
The same test step can be done using different input parameters resulting in different test results.

An example of the above would be doing a login with a valid and an invalid password.
In the first case the login would be successful in the second an error message would be shown.

MyITest4U

The above considerations are used to build MyITest4U. The main components of MyITest4U are:

  • GUI Element Collector
  • Test Builder
  • Test Runner
  • Test Analysis
  • Test Maintenance
  • Test Generator

GUI Element Collector

The GUI Element Collector collects the GUI elements of an application and stores them in the MyITest4U database.
It has to run always as first step.
Each GUI element gets an unique identifier and all its properties are written to the database.

Test Builder

The Test Builder is used to build tests. Each test contains one or more test steps.
Each test step couples a GUI element to an action.
Each GUI element used in the Test Builder has to come from the MyITest4U database.
Each action has to come from a predefined list of actions.
The input parameter and check points belonging to a test step are stored in a predefined parameter file.

Test Runner

The Test Runner implements the following three steps:

  1. Find a GUI element
  2. Execute the action
  3. Check the result

Further the Test Runner contains an inner and outer loop.
The inner loop goes through all test steps.
The outer loop goes through all parameter variations belonging to a test.

Test Analysis

Test Analysis is done by parsing the test log file. The test results can be stored in the MyITest4U database.

Test Maintenance

As a matter of fact things are changing.

  • a new look is desired
  • fine tuning of your application needs to be done
  • new features are build

Your automated tests have to be able to cope with these changes.
MyITest4U is build to help you with this.
The following steps need to be done when your application changes:

  1. Collect all GUI elements of the new release.
  2. Map all used GUI elements from the old release to the new one.
  3. Fix all changes in the test step sequences.
  4. Fix the parameter files.

MyITest4U supports you in all of the above steps and keeps test maintenance time to a minimum.

Automatic Test Generation

You believe that is impossible.
MyITest4U not only makes Automatic Test Generation possible.
MyITest4U has Test Generators build in.
Further it is possible to build your own Test Generators.
Talk with your developers. They will love it.

Enough talking.

Give MyITest4U a Try