Creating Tests

Hands-on tutorial

Build a reusable login test visually—generate executable test code automatically without writing scripts.

Role: QA authors and developersTime: 15-20 minutesOutcome: a working, reusable login test with live Gherkin preview

Open Quick Start Open Running Tests

Before you begin

• AppraiseJS is running locally.
• You have a reachable login page or another small smoke-test target.
• You know which environment URL and credentials are safe to use locally.

What you’ll build

A reusable smoke scenario

You will create a reusable login test that: - Works across environments - Uses centralized locators - Generates executable test code - Can be rerun anytime from the Test Runs screen

Step-by-step procedure

UI path

Modules → Environments → Locators → Test Suites → Test Cases

How to think about Test Cases in AppraiseJS

Think of Test Cases like this:

• Modules & Suites → organize your tests
• Locators → define what to interact with
• Flow Builder → define what happens
• Scenario Preview → shows the generated test code in real time

You are not writing scripts. You are designing test logic.

Test cases are where your test logic comes to life. Instead of writing scripts, you visually assemble reusable steps into a complete scenario. Each step represents an action or validation, and together they form a flow that can be executed reliably across environments.

Enough theory, let’s get hands-on.

1. Create a module named Authentication so the scenario has a clear home in the product model.

   
   
   

2. Create a new environment named Local with the application base URL you want to test.

   
   
   

3. Open Locators -> Create and launch the Chromium picker from that saved environment.

   
   
   

4. Capture locators as per your needs.

5. Create suite Auth Smoke under the Authentication module.

   
   
   

6. Navigate to Automate -> Test Cases -> Create or click the Create Test button from the dashboard.

7. Before building the flow, fill in the basics:

   • Title → short identifier (e.g. Login success)
   • Description → one sentence describing what this validates
   • Test Suite → select Auth Smoke (required)
   • Tags (optional) → useful later for filtering test runs

8. This is where AppraiseJS becomes powerful.
   The flow builder lets you construct your test visually:

   • Each node = one action or assertion
   • Nodes connect to form a complete scenario
   • Parameters make each step reusable

   As you build, Appraise automatically generates the Gherkin scenario—so what you see is always aligned with what will run.

9. Another important component of test case creation form is the Scenario Preview panel. It shows a preview of the gherkin output that will be generated from the test case flow as you build it.

10. Fill up the required fields by adding a test case title, description and assign the test case to the Auth Smoke suite.

11. Click on the Add Node button to add the first step to navigate to the selected environment base URL so the case is portable across environments.

12. Add input step nodes for email and password using the captured locators.

13. Add a click step node for the submit button.

14. Add an assertion step node that checks the welcomeBanner visibility is true.

    
    

    Here is a demo of the test case editor in action.

    
    

Quick sanity check

At this point, you should have:

• A navigable flow (start → input → click → assertion)
• No missing parameters
• A live Gherkin preview updating on the right

If you see this, you have already built a complete automated test.

15. Save the case and re-open it once to confirm every parameter, locator reference, and suite relationship still looks correct.

Here is a screenshot of the saved test case editor state with ordered steps and filled parameters.

Checkpoint

• The case opens with a complete ordered flow and no missing required parameters.
• Every referenced locator exists and belongs to a route-aware locator group.
• The suite, module, and environment names are clear enough that another team member could reuse them later.

AppraiseJS is designed so your test logic stays clear, reusable, and never buried inside scripts.

Common mistakes

• Creating locators before deciding which environment or route they should belong to.
• Saving a case with literal values that should have been environment-driven or reusable.
• Mixing multiple business outcomes into one case instead of one clear scenario.
• Naming assets too generically, which makes future reuse harder.

Next step

Move to Running Tests to execute the scenario either by tags or by explicit case selection.