'Test Scripts' are the lowest level of an automation artifact in Worksoft SaaS within a project. Test Scripts are akin to the lowest level of Lego blocks. 

Test Scripts are maintained within a project-level 'Test Script Library' within your Worksoft SaaS domain are accessible by you and your peers that have access to a project within your Worksoft SaaS domain. You all can collaborate to create and maintain the test scripts.

One or more Test Scripts in your Script Library can be assembled into a higher level of an automation entity called 'Test Scenario'. One or more Test Scenarios can be assembled into an even higher level of an automation unit called 'Run Definition', which then can be scheduled for execution from within Worksoft SaaS application or from your CI/CD tool on a set schedule.  

The primary vehicle for you to use to create test scripts is QaSCRIBE, our cloud-based test script "authoring" tool that works as a browser add-on for Google Chrome and Mozilla Firefox.

You can 'unit test' (or certify) your Test Scripts and even Scenarios and Run Definitions 'locally' on your Windows or Macintosh desktop/laptop using Chrome and Firefox browsers. Once you are have 'certified' your tests using local executions, you can then schedule the Run Definitions (and if needed even the Scenarios) for execution on the Worksoft SaaS Cloud. 

After you read this you may want to see:

• QaSCRIBE Overview
• Installing QaSCRIBE
• Test Scripts module home screen
• Understanding how to build test scripts using QaSCRIBE
• Understanding how to run tests "locally" using QaSCRIBE
• Understanding how to debug tests executed "locally" using QaSCRIBE