Question 1

Targeting Elements

Accepted Answer

1 - Matching by text This matches by using either the text on screen, or aria labels. For example I.click("login") or I.fill("First Name","John") One thing useful is that when there are multiple text of the same text, it is sometimes useful to do an I.see("Unique text") near the target text to interact with, think of it as instructing a user over the phone 😉

2 - Matching by HTML/CSS class name Elements can be selected using HTML/CSS class name, with a dot prefix. For example I.click(".login-button")

3 - Matching by HTML/CSS ID Elements can be selected using HTML/CSS ID, with a hash prefix. For example I.click("#close")

4 - Matching by XPath Elements can be selected using XPath. For example I.click('//*[@id="tsf"]/div[2]/div[3]/center/input[1]')

Additional Note - Running actions inside an iframe Finally when interacting with elements inside an iFrame, especially with salesforce, SAP, Shopify. You can improve the accuracy by running actions within a selected iframe context. For example:

UI.context("#unique-iframe-id", function() {
   I.click("Button inside iframe")
   //... other actions
})

Question 2

Handling a DATE PICKER

Accepted Answer

Date pickers may or will vary from each website, the complexity of the date picker is based on how the calendar or the date picker of website has been designed. Some are may be as simple as typing in the dates by using the I.fill or I.type.

So this guide will help the user or at least give an idea on how to handle the date picker should the user encounter a simple or complex one.

Without further ado let's get to the step by step procedure

Fill Date Picker using text input commands

Q: Targeting Elements

1 - Matching by text This matches by using either the text on screen, or aria labels. For example <code>I.click("login")</code> or <code>I.fill("First Name","John")</code> One thing useful is that when there are multiple text of the same text, it is sometimes useful to do an I.see("Unique text") near the target text to interact with, think of it as instructing a user over the phone 😉 2 - Matching by HTML/CSS class name Elements can be selected using HTML/CSS class name, with a dot prefix. For example <code>I.click(".login-button")</code> 3 - Matching by HTML/CSS ID Elements can be selected using HTML/CSS ID, with a hash prefix. For example <code>I.click("#close")</code> 4 - Matching by XPath Elements can be selected using XPath. For example <code>I.click('//*[@id="tsf"]/div[2]/div[3]/center/input[1]')</code> Additional Note - Running actions inside an iframe Finally when interacting with elements inside an iFrame, especially with salesforce, SAP, Shopify. You can improve the accuracy by running actions within a selected iframe context. For example: <pre><code class="javascript language-javascript">UI.context("#unique-iframe-id", function() { I.click("Button inside iframe") //... other actions }) </code></pre>

Q: How do I test with external login providers

For production applications with production accounts This is typically acceptable for low testing loads (like 1 to 3 a day). However as with most automation. Eventually reCAPTCHA will be triggered. For most login providers, uilicious is considered a "bot" from the login provider point of view. And will be treated as such. While there might be ways to do so in the black market, we do not support such practises. Hence, we would instead recommend the following options, for testing with external login providers. Have an internal login provider? Limit your external login provider test to once a day. And depend on your internal login provider instead to do the bulk of testing. This allows the external login test to keep within the boundaries of a low test load (1 to 3). This approach can be used together with the various other options listed. Facebook: configure testing accounts for your application See: https://developers.facebook.com/docs/apps/test-users/ Facebook allow the creation of up to 2000 test users for an application. Ideally using an email domain you control, with a secure password as these accounts would still be valid in your production environment. With limitations. Create multiple dedicated test accounts By splitting up your testing load across multiple accounts, you can manage the rate which reCAPTCHA will trigger. This is particularly useful for dedicated testing twitter accounts, that are limited purely to login (no tweets, nor messa

Step I: Create a Test File for the Datepicker

Step II: Create datepicker flow using Text Input commands such as I.fill

I.goTo - goes to the website where the datepicker is located

I.see - validates that you are in the Datepicker page/module
I.fill - fills the "Date" input box
I.pressEnter - confirms the date

For reference here's the link to the above script (datePicker)

Fill Date Picker by clicking on the Calendar

NOTE: This part requires knowledge on Javascript/HTML/CSS. Should you be having a hard time you should ask your developers for assistance.

Question 3

How to RUN or REUSE test scripts from another test script

Accepted Answer

Using the TEST.run() command will allow the user to **RUN **or **REUSE **the test script in another test script.

Why should you use TEST.run command?

Using the TEST.run command will allow the user to use 1 test on multiple or different test scripts, this will greatly help the user to have a more efficient way of testing and editing the test.

Sample: A Login module that will be used in multiple cases or in different cases. Instead of creating a login module in each individual test scripts the user can create 1 test file for the login module and use the TEST.run command in other test script to import the login module as seen below.

This is a Step by Step procedure on how to use the TEST.run command in a basic way.

Step I: Create the "Login Module" test file and create the login flow inside it

Step II: Create another Test File where the TEST.run will be execute

NOTE: The placement of the TEST.run is important in this kind of scenario, when the TEST.run is placed on the lower part, the test will execute it after executing the I.wait and I.see commands.

Step III: Run and Observe the Test…

Notice that the Login Module flow (highlighted in the red box) ha

Question 4

How to set secure test data

Accepted Answer

If you want to pass sensitive test data like passwords to the test runner, use DATASETs to setup secret test data instead of writing it into your test script.

Secret test data will only be known to you, and will be masked in the test reports.

Here's an example, using this test to sign up for GitHub:

Use DATA. variables for the access credentials which we want to replace using the datasets

I.goTo("https://github.com")
I.click("Sign up")
I.see("Join GitHub")
I.fill("Username", DATA.username) // to be replaced with dataset
I.fill("Email", DATA.email) // to be replaced with dataset
I.fill("Password", DATA.password) // to be replaced with dataset
I.click("Create an account")

Click on "Add Dataset" in the Run toolbar

Set the values for your DATA. variables in the Dataset. Remember to change the password data from Public to Secret. Save the dataset when you are done.

Finally, select the dataset and run your tests.

As you can see in the report, the access credentials have been taken from the "Bruce Wayne" dataset, and the value of password has been masked because it is a secret test data.

Question 5

How do I test with external login providers

Accepted Answer

For production applications with production accounts This is typically acceptable for low testing loads (like 1 to 3 a day). However as with most automation. Eventually reCAPTCHA will be triggered.

For most login providers, uilicious is considered a "bot" from the login provider point of view. And will be treated as such.

While there might be ways to do so in the black market, we do not support such practises.

Hence, we would instead recommend the following options, for testing with external login providers.

Have an internal login provider? Limit your external login provider test to once a day.

And depend on your internal login provider instead to do the bulk of testing. This allows the external login test to keep within the boundaries of a low test load (1 to 3). This approach can be used together with the various other options listed.

Facebook: configure testing accounts for your application See: https://developers.facebook.com/docs/apps/test-users/

Facebook allow the creation of up to 2000 test users for an application. Ideally using an email domain you control, with a secure password as these accounts would still be valid in your production environment. With limitations.

Create multiple dedicated test accounts By splitting up your testing load across multiple accounts, you can manage the rate which reCAPTCHA will trigger. This is particularly useful for dedicated testing twitter accounts, that are limited purely to login (no tweets, nor messa

Question 6

Change of billing email and address

Accepted Answer

If you would like to change the billing email and address shown on your invoices, just contact us via chat or email us at support@uilicious.com, and we'll have it updated right away.

Frequently Read Articles

Browse All Categories