admin

NocoDB provides an intuitive spreadsheet interface for creating online databases, either from scratch or by connecting to any Postgres/MySQL. With strong open source ethos – NocoDB caters to businesses of all sizes & shapes . Be it Agencies, Startups, Small Medium Businesses and Enterprises.

An ideal way to test the application will be using testRigor end-to-end testing.

 

E2E for NocoDB

NocoDB turns any SQL database into a spreadsheet-like app. Because it’s a rich, client-heavy UI backed by APIs and a DB, the highest risk sits in cross-layer workflows: onboarding (first-run setup), base/project creation, table/column operations, permissions, and CRUD via the UI. End-to-end (E2E) tests validate those flows from a real user’s perspective.

 

testRigor

testRigor lets you write tests in plain English and runs them in the cloud against your app without brittle CSS/XPath selectors. That means:

• Readable tests your team (and NocoDB contributors) can review.

• Resilient element targeting by visible text, labels, and relative anchors.

• Zero local browser infra; run locally or inside CI (we tunnel localhost for PR checks).

• Artifacts (video, screenshots, JUnit) for fast triage.

 

Setting up test suite

With a NocoDB account created and with access to the application, now we can create a test suite to start performing end to end test cases, following the following steps:

 

Step 1: Log in to your testRigor app with your credentials.

Step 2: Set up the test suite for the website testing by providing the information below:

• Test Suite Name: Provide a relevant and self-explanatory name.
• Type of testing: Select from the following options: Desktop Web Testing, Mobile Web Testing, Native and Hybrid Mobile, based on your test requirements.
• URL to run test on: Provide the application URL that you want to test.
• Testing credentials for your web/mobile app to test functionality which requires user to login: You can provide the app’s user login credentials here and need not write them separately in the test steps then. The login functionality will be taken care of automatically using the keyword login.
• OS and Browser: Choose the OS Browser combination on which you want to run the test cases.
• Number of test cases to generate using AI: If you wish, you can choose to generate test cases based on the App Description text, which works on generative AI.

[IMAGE]

 

• Step 3: Click Create Test Suite.

On the next screen, you can let AI generate the test case based on the App Description you provided during the Test Suite creation. However, for now, select do not generate any test, since we will write the test steps ourselves.

 

• Step 4: To create a new custom test case yourself, click Add Custom Test Case.

[IMAGE]

 

• Step 5: Provide the test case Description and start adding the test steps.

[IMAGE]

 

For the NocoDB application under test, we will perform below test steps:

• Login to the application;
• Create a table;
• Add a new record.

 

Test Case: Creating new table and records

Step 1: We will add test steps on the test case editor screen one by one.

testRigor automatically navigates to the website URL you provided during the Test Suite creation. There is no need to use any separate function for it. Here is the website homepage, which we intend to test.

[IMAGE]

 

To have access to the main page, we need to login to our account. For that, testRigor has a built-in reusable rule “login”, that will use the variables “Username” and “Password” defined in the test suite creation to perform the login function.

First, we want to create our new table. Unlike traditional testing tools, you can identify the UI element using the text you see on the screen. You don’t need to use any CSS/XPath identifiers. For this function, we see the text “Create New?” So, to activate the search box, we will use the exact text in the first test step using plain English:

click “Create new”

Step 2: Once the cursor is in the button, we will have to select what we want to create, specify the name and then confirm the creation.

click "table"

type "Table - Test"

click "create table"

[IMAGE]

 

 

Step 3: We can validate that the table was created with a simple step, and it will be shown in the screenshot.

[IMAGE]

 

Step 4: For the final steps, now we can add new records to the table we just created before.

type "test 1"

type enter

type "test 2"

type enter

type "test 3"

[IMAGE]

Complete Test Case

Here is how the complete test case will look in the testRigor app. The test steps are simple in plain English, enabling everyone in your team to write and execute them.

[IMAGE]

Click Add and Run.

 

Execution Results

Once the test is executed, you can view the execution details, such as execution status, time spent in execution, screenshots, error messages, logs, video recordings of the test execution, etc. In case of any failure, there are logs and error text that are available easily in a few clicks.

You can also download the complete execution with steps and screenshots in PDF or Word format through the View Execution option.

[IMAGE]

 

testRigor’s Capabilities

Apart from the simplistic test case design and execution, there are some advanced features that help you test your application using simple English commands.

• Reusable Rules (Subroutines): You can easily create functions for the test steps that you use repeatedly. You can use the Reusable Rules to create such functions and call them in test cases by simply writing their names. See the example of Reusable Rules.
• Global Variables and Data Sets: You can import data from external files or create your own global variables and data sets in testRigor to use them in data-driven testing.
• 2FA, QR Code, and Captcha Resolution: testRigor easily manages the 2FA, QR Code, and Captcha resolution through its simple English commands.
• Email, Phone Call, and SMS Testing: Use simple English commands to test the email, phone calls, and SMS. These commands are useful for validating 2FA scenarios, with OTPs and authentication codes being sent to email, phone calls, or via phone text.
• File Upload/ Download Testing: Execute the test steps involving file download or file upload without the requirement of any third-party software. You can also validate the contents of the files using testRigor’s simple English commands.
• Database Testing: Execute database queries and validate the results fetched.

testRigor enables you to test web, mobile (hybrid, native), API, and desktop apps with minimum effort and maintenance.

 

Additional Resources

• Access testRigor documentation to know about more useful capabilities
• Top testRigor’s features
• How to perform end-to-end testing

 

Setting up GitHub CI/CD Integration

For automated testing in your GitHub repository, you’ll need to configure your testRigor credentials as GitHub secrets. This approach differs from local testing by using GitHub’s secure environment variables instead of a local .env file.

Step 1 – Add GitHub Secrets

1. Go to your GitHub repository
2. Click on “Settings” → “Secrets and variables” → “Actions”
3. Add the following:
   • As a secret:
     • NOCODB_AUTH_TOKEN: Your testRigor auth token (keep this private)
   • As variables:
     • NOCODB_TEST_SUITE_ID: Your testRigor Test Suite ID
     • NOCODB_BASE_URL: Your NocoDB website URL

For further information on creating secrets and variables in GitHub Actions, you can check the official GitHub documentation on secrets and variables.

Required GitHub Secrets and Variables:

• NOCODB_TEST_SUITE_ID: Your testRigor Test Suite ID (e.g., 12345)
• NOCODB_AUTH_TOKEN: Your testRigor auth token (format: ########-####-####-####-############)
• NOCODB_BASE_URL: Your NocoDB website URL (e.g., https://yourstore.com)

Step 2- Use in GitHub Actions

In your GitHub Actions workflow file, reference these secrets like this:

- name: Run testRigor Tests

  run: bin/mftf run:testrigor

  env:

    NOCODB_AUTH_TOKEN: ${{ secrets. NOCODB_AUTH_TOKEN }}

     NOCODB_TEST_SUITE_ID: ${{ vars. NOCODB_TEST_SUITE_ID }}

     NOCODB_BASE_URL: ${{ vars. NOCODB_BASE_URL }}

Key Difference: While local testing uses a .env file, CI/CD uses GitHub’s secure secret management system, ensuring your credentials are encrypted and only accessible to authorized workflows.

 

Troubleshooting Tips

If you find any issues:

• Make sure your NocoDB site is running and accessible at the URL you specified
• Check your .env file – ensure all three values are correct and there are no extra spaces
• Verify your testRigor account – make sure you can log in and see the test suite
• Check your internet connection – testRigor needs to download some tools on first run

If you need to start over, simply delete the .mftf-tools folder and run the command again.

 

Conclusion

With NocoDB, you can turn any SQL database into a spreadsheet-style app and move from setup to usable data fast. To keep those experiences reliable at scale, pair it with end-to-end automation: testRigor lets you write resilient, plain-English tests and run them in CI with clear artifacts. Before adopting, assess your flows and coverage needs, then choose the configuration that best fits your team and environments.

	Achieve More Than 90% Test Automation
	Step by Step Walkthroughs and Help
	14 Day Free Trial, Cancel Anytime