• Significance of the 'Name' of a test script
  
• Assigning the 'Name' to a test script (during script creation/upload)
  
• Assigning the 'Name' to a test script - Web Apps
  
• Assigning the 'Name' to a test script - Native/Mobile Apps
  
• Changing (editing) the 'Name' of a test script - Overview
  
• Editing the 'Name' of a test script in 'WIP' status
  
• Editing the 'Name' of a test script in 'WIP of an Active' status
  
• Searching for (finding) a test script based on its 'Name'
  

Significance of the 'Name' of a test script:

The 'Name' is a string you assign to uniquely identify each of your test scripts within a project. The name has to reflect the 'main' purpose the test script serves within your test automation project.

The name can be any combination of alpha numeric characters, not exceeding 128 characters, excluding the following characters - single quote, greater than and less than.

As mentioned earlier, you cannot have more than one test script in a project with the same name. However, you can use the same name for a test script in a different project, if the need arises.

Worksoft SaaS recommends that you keep the name as descriptive and intuitive as possible for not only you (the person assigning it) but to your peers that have access to the project. Hence, you may want to avoid acronyms or abbreviations as much as possible. It will also make sense to follow some sort of a consistent naming convention for all your test scripts.

Assigning the 'Name' to a test script (during script creation/upload) - Overview:

You assign the name to a test script that you author to test 'Web Applications for Desktop and Mobile Browsers' and 'Native or Hybrid Mobile Apps' on the screen that comes up when you (browser) upload the test script(s) you create using QaSCRIBEor using Excel respectively into the Worksoft SaaS application.

For test scripts that you author with QaSCRIBE, the name is defaulted to the name of the test script file name that you uploaded and can be overwritten. We actually strongly recommend that you carefully craft a name that suits the purpose served by the test script. Lot of times when you are saving a test script that you author using QaSCRIBE, you may not pay attention to the name you give the test script (in XML format) that you save to your local machine. It therefore becomes essential that you assign an appropriate name to your test script as part of uploading it into Worksoft SaaS application.

Assigning the 'Name' to a test script - Web Apps:

The image below show how you enter the name for a test script that tests 'Web Applications for Desktop and Mobile Browsers':

Assigning the 'Name' to a test script - Native/Hybrid Apps:

The images below show how you enter the name for a test script that tests 'Native or Hybrid Mobile Apps':

Changing (editing) the 'Name' of a test script - Overview:  

You can change the name of a test script as long it is in the 'WIP' (Work In Progress) status of the first version of the test script and you are in the 'Edit' mode of the test script. Lets assume that you develop and unit test your test script using QaSCRIBE on Firefox. Then you upload it into Worksoft SaaS application, and then while its status is 'WIP', you attempt to certify that the script works well on other desktop and mobile browsers (like Chrome, Safari, Mobile Safari, Android Chrome, etc). You may need a day or two (or however long it takes for you) to finish the edits you need to your script to make it execute well against all browsers of interest. During this period, you are free to change the name of the test script, if a need arises.

In Worksoft SaaS, you can 'activate' a 'WIP' version of a test script. That creates the test script in 'Active' status. When you edit an 'Active' version of the test script, a new 'WIP' version is created for it while retaining the 'Active' version. That WIP is called the 'WIP of an Active' version, and Worksoft SaaS does NOT allow you to change the name of the test script on the 'WIP of an Active' version.

You can only change the name on the 'WIP' version before you activated it the first time. Therefore it becomes critical that you think about the appropriate name and follow a consistent naming convention (that you discuss with your peer automation developers ahead of time).

Editing the 'Name' of a test script in 'WIP' status:

Editing the 'Name' of a test script in 'WIP of an Active' status:

You are not allowed to change the name of a test script when the status of the test script is 'WIP of an Active'. You can only view the test script name that was previously assigned when the script was in 'WIP' status.