How to create a good test page

Hello everyone, here’s the Skuid approved method for creating a good test page.

Why are test pages important?

A simple test page is easy to share with other Skuid users. It allows another person to easily reproduce your use case and, in the case of an issue, identify what's going on. Because Skuid pages are stored as XML, it’s easy to transfer Skuid pages between environments, especially if you follow the guidelines below.

What makes a good test page?

A good test page consists of the following:

  1. At the top of the page, a description of what's going on: this can be a list of steps to reproduce the issue (in the case of a product defect) or a description of the change (in the case of a feature/improvement).

    • If the issue requires a specific environment configuration (i.e. a Salesforce Validation Rule), include specific steps for setting up the configuration.
  2. If at all possible, use Ui-Only models because they will work in any Skuid environment regardless of the Data Sources connected. If you do need to use a Data Source:

    • Use Skuid standard data entities (e.g. "Page").

    • If you cannot use Ui-Only models, use Salesforce Standard Objects/Fields when at all possible.

  3. Illustrate the issue at hand in the simplest, most concise manner possible (i.e. no "kitchen sink" pages). The goal is to reduce noise such that only the behavior which needs to be addressed is presented in the Test Page:

    • No custom Themes or Design Systems (unless it's related to Themes or Design Systems)

    • No JavaScript (unless it's related to JavaScript)

    • No custom CSS

    • No Models other than ones required to reproduce the behavior

    • No Model Actions (unless it's related to Model Actions)

    • No Action Framework Sequences (unless it's related to Action Framework Sequences)

    • No Components that are not related to the specific issue being reported

  4. Verify the behavior in V1/V2 (if applicable). Provide a Test Page for all API Versions where the behavior presents itself.

  5. Include the XML for all Test Pages with your post (i.e. don't link to pages in live environments).
Also, here are some goodies for you - test page templates for v1 and v2!

Test Page Template V1:
            <h1>Testing Procedure</h1><ul> <li>Preview page</li> <li><strong>Expected Results:</strong></li></ul>                                       
```

Test Page Template V2: