Page Comparison

...

This sequence is adjustable according to your specific needs.

Before we get in to creating objects, let’s cover some fundamentals.

Rules for Duplicate Objects

You can add an existing object under a different page, but QAS renames the object automatically. This is to avoid confusion when referring to the objects in your test cases.

When you add an object with the same name and same locator values manually, QAS either does not allow it or might rename the object automatically depending on the time span. This is to ensure the unique identification of each object.

You cannot add the same object with the same name and same locator values under the same page. This is to prevent ambiguity during test execution.

Use Case for Duplicate Objects:

Suppose you are testing a web application that has multiple pages, and each page has a Submit button with the same ID submitBtn.

1. If you try to add the "Submit" button object from the second page while it already exists from the first page, QAS will automatically rename the second object to avoid confusion. For example, it might rename it to submitBtn_1.

2. If you try to add another "Submit" button object on the first page with the same ID `submitBtn, QAS will not allow it to avoid ambiguity during test execution.

   1. If you try to add a Submit button object with the same ID submitBtn but manually change the name to SubmitButton, QAS might still rename it automatically if it detects that the locator values are the same. This is to ensure that each object can be uniquely identified not just by its name but also by its locator values.