A powerful open source test automation platform for Web Apps, Mobile Apps, and APIs

Last update: Dec 31, 2022

Overview

Getting started ⋅ Docs ⋅ Tutorials ⋅ Discussions ⋅ Discord ⋅ YouTube

Overview

Testsigma is an open-source, extensible test automation platform that works out of the box. Rapidly(5X faster) automate web, mobile app, and API tests in plain English.

Eliminate complex setups, multiple tools and frameworks.
Let everyone write tests 5X faster using plain English.
Smart test recorder auto-converts user actions into editable steps.
Automate end-to-end testing for web, mobile apps & APIs.
Minimal to no maintenance of tests and frameworks
Built-in test data management for parameterized testing
Seamless integrations with CI/CD, bug reporting, product management tools, & collaboration tools & test labs for continuous testing.
Extend the platform with 100+ pre-built add-ons (for custom actions, data generators, integrations) or build your own with Testsigma SDKs.

Quick start: One click deployment on Testsigma Cloud

The easiest way to start your automation journey is with Testsigma Cloud.

Once you deploy, you can follow the below tutorials to get started

Other deployment options

We have 2 more deployment options to choose from

Features

Test Development

Write code-agnostic, human-readable tests in plain English.
Generate airtight test scripts for web and mobile apps using Test Recorder.
Integrate automated API calls within your functional/UI test steps.

Data-Driven/Parameterized Testing

Upload test data sets as (XLS) files or create within Testsigma.
Use built-in data generators for mock test data.
Create your own custom data generators as add-ons.

Results & Reports

Debug using screenshots, videos, text logs, and more.
Generate custom reports at test, module, test suite, and device/system levels.

Integrations

Integrate with any CI tool to run regression tests at every build.
Integrate with Collaboration tools, Bug Reporting tools, Product Management tools, Cloud based Test Labs

Unified Platform

Automate Web, Mobile Web, Android, iOS apps, and API testing using one platform

Visual Testing

Enable visual testing with a toggle while creating a test plan.

See more on our website

Build & extend the platform with Add-ons

Add-ons are custom extensions built and shared by the Testsigma Community at the Add-ons Marketplace. Add-ons are built to automate unique user actions and test automation scenarios that are not possible with Testsigma’s default actions.

You can build your own add-on using Testsigma SDK.

Types of add-ons supported in Testsigma

Custom Actions: Testsigma provides a set of comprehensive, built-in addons that lets you automate most user actions in simple English. But sometimes you may need to automate actions unique to your AUT. For this, you can build custom add-ons to automate unique actions. See: How to build a custom action in add-ons.
Custom Data Generators: Testsigma contains default Data Generators to generate instant test data for your automation scenarios. You can also build custom data generators. See: How to build a custom data generator.
Conditional If: You can create an action to execute a sequence of steps if the condition is matched. You can write your own logic for the conditional if. See: How to add conditional if actions.
While Loops: You can create an action to execute a sequence of steps until the condition is matched. You can write your own logic for the conditional if. See: How to add while actions.

Tutorials

Here are the latest tutorials and videos for you to learn more about Testsigma:

Visit our tutorials to explore more.

Roadmap

Check out our roadmap to see what we are or will be working on.

Support & Troubleshooting

The documentation and community will help you troubleshoot most issues. If you have encountered a bug, you can contact us using one of the following channels:

💬 Support & feedback: Discord
📚 Find a solution in our Documentation
🐛 Issue & bug tracking: GitHub issues
👾 Ask for help on our Forum
💬 Talk to us on our website chat

We are committed to fostering an open and welcoming environment in the community. Please see the Code of Conduct.

If you want to report a security issue, please read this.

Join our community

Engage with test automation Architects, SDETs, Testers, and Developers around the world. Get the latest product updates. Discuss testing philosophies and more. Join the Testsigma Community on Discord.

Stay up to date

We release new features every month. Sign up for our newsletter by using the link below. We send newsletters only once a month.

https://testsigma.com/whats-new

Contribute

We love our contributors! If you'd like to contribute anything from a bug fix to a feature update, start here:

📖 Read our Contribution Guide
🧩 Set up your local environment
👾 Explore some good first issues
📕 Read our Code of Conduct

License

Testsigma is available under the Apache License 2.0 (Apache-2.0).

Comments

[Bug]: Unable to view test cases and execute test cases after upgrading
Is there an existing issue for this?

[X] I have searched the existing issues

What is the current behavior?

I am running Testsigma CE in Docker and after upgrading from v2.0.1 to v2.1 I am no longer able to see my test cases. I am also seeing errors in the log for my agent.

Errors are: 2022-09-23 00:43:06 981358AE6F094D7188E9813957868068 ERROR SqlExceptionHelper:logExceptions:142 qtp1586095399-323 Unknown column 'testdevice0_.prerequisite_test_device_result_id' in 'field list'

2022-09-23 00:43:46 EFA106077EF640E4B723D72C3CBAEE12 ERROR SqlExceptionHelper:logExceptions:142 qtp1586095399-462 Unknown column 'testdata0_.passwords' in 'field list'

I can see for V28__test_device.results.sql file has been modified to include a column prerequisite_test_device_result_id, however this change is never reflected in any of the migration script, so it will never get picked up when upgrading.

Also in v17__test_data.sql, the column passwords

What is the expected behavior?

When upgrading between versions of TestSigma, database changes should be picked up as a migration step.

Steps To Reproduce

In docker-compose, run v2.0.1 as the image and upgrade to v2.1

Version

Testsigma Community Edition
bug
opened by snapshotleisure 6
[Bug]: Not able to start the testsigma server
Is there an existing issue for this?

[X] I have searched the existing issues

What is the current behavior?

when i started the API server getting the below error on MySQL connector

and when I start the Agent and getting the below error as 502

What is the expected behavior?

The UI should launched

Steps To Reproduce

Download the testsigma bundle

Install the MySql

Setup the env variable for MYSQL_PASSWORD

Start the Nginx

And Start the server then start the Agent

Version

Testsigma Community Edition
bug
opened by sseenivasan89 2
[Bug]: Unclear error message when user is trying to delete an "Out of Sync Agent"
Is there an existing issue for this?

[X] I have searched the existing issues

What is the current behavior?

Refer to the bug report: https://app.birdeatsbug.com/sessions/TMrutD_qAt_n7WEnqOZheZWmXWPPDQGtp3tJyjyIclCZ

What is the expected behavior?

Refer to the bug report: https://app.birdeatsbug.com/sessions/TMrutD_qAt_n7WEnqOZheZWmXWPPDQGtp3tJyjyIclCZ

Steps To Reproduce

Refer to the bug report: https://app.birdeatsbug.com/sessions/TMrutD_qAt_n7WEnqOZheZWmXWPPDQGtp3tJyjyIclCZ

Version

Testsigma Community Edition
bug
opened by parwalrahul 2
[TOS-927] Ability to import TestProject test cases
Supports imports of yaml and zip files exported from test project. Note that this is a best effort migration and users have to review the test cases after migration and also fill up the non-existing test step mappings

Checklist:

[x] My code follows the style guidelines of this project

[x] I have performed a self-review of my own code

[x] I have commented my code, particularly in hard-to-understand areas

[x] My changes generate no new warnings

[x] Changes would cause existing functionality to not work as expected
opened by tarun-testsigma 1
TRD-164-Added method to wait for ajax calls to complete
Description

Ajax calls:

Ajax is a way for the client-side browser to communicate with the server (for example: retrieve data from a database) without having to perform a page refresh.

How can we figure out if a website is making Ajax calls?

Go to any website and open the console

Type ‘jQuery.active’, if it returns a value, then the website is using jQuery to make ajax calls.

How can we know if the ajax calls are complete:

From the browser console, if ‘jQuery.active’, returns 0, then, we can be sure that ajax calls are complete

Checklist:

[x] My code follows the style guidelines of this project

[x] I have performed a self-review of my own code

[x] I have commented my code, particularly in hard-to-understand areas

[ ] I have made corresponding changes to the documentation

[x] My changes generate no new warnings

[ ] Changes would cause existing functionality to not work as expected

[ ] I have added tests that prove my fix is effective or that my feature works

[ ] New and existing unit tests pass locally with my changes

Mobile:

Web:
opened by vikramvr20 1
Dev sync with master
Pull Request Template

Use this template to quickly create a well written pull request. Delete all quotes before creating the pull request.

Description

Please include a summary of the changes and which issue has been fixed.

Fixes # (issue)

if no issue exists, please create an issue and discuss with the maintainers before comitting.

Checklist:

[ ] My code follows the style guidelines of this project

[ ] I have performed a self-review of my own code

[ ] I have commented my code, particularly in hard-to-understand areas

[ ] I have made corresponding changes to the documentation

[ ] My changes generate no new warnings

[ ] Changes would cause existing functionality to not work as expected

[ ] I have added tests that prove my fix is effective or that my feature works

[ ] New and existing unit tests pass locally with my changes
opened by rajesh-testsigma 1
[Docs & Tutorials]: how to use open source version
Is there an existing issue for this?

[X] I have searched the existing issues

Doc/tutorial link

No response

Explain the problem

[Docs & Tutorials]: how to use open source version i am no able to start this project usage open source version

Your inputs to improve

need get started step
opened by Sky-bits 1
v1.9.0
[x] Supporting Test executions on IOS Simulators

[x] Test authoring using IOS Simulators

Checklist:

[x] My code follows the style guidelines of this project

[x] I have performed a self-review of my own code

[x] I have commented my code, particularly in hard-to-understand areas

[x] I have made corresponding changes to the documentation

[x] My changes generate no new warnings

[x] Changes would cause existing functionality to not work as expected

[x] I have added tests that prove my fix is effective or that my feature works

[x] New and existing unit tests pass locally with my changes
opened by PratheepV 1
[Bug]: Incorrect Upgrade Message Popup as well as Latest Version # for Testsigma Agent
Is there an existing issue for this?

[X] I have searched the existing issues

What is the current behavior?

The warning or info popup on the Agents section from the OS version shows the current version as: 1.7.0 and the latest version as 1.1.0

Refer screenshot below:

This seems to be a problem with the versioning of the testsigma server or with the popup.

Needs to be analyzed.

What is the expected behavior?

If we are on the latest version, it should not ask us to upgrade to a lower version.

Steps To Reproduce

Test Sigma OS > Agents > Warning

Set up everything in the latest configuration.

Version

Testsigma Community Edition
bug
opened by parwalrahul 1
Updated README.md file
Pull Request Template

Use this template to quickly create a well written pull request. Delete all quotes before creating the pull request.

Description

Please include a summary of the changes and which issue has been fixed.

Fixes # (issue)

if no issue exists, please create an issue and discuss with the maintainers before comitting.

Checklist:

[ ] My code follows the style guidelines of this project

[ ] I have performed a self-review of my own code

[ ] I have commented my code, particularly in hard-to-understand areas

[ ] I have made corresponding changes to the documentation

[ ] My changes generate no new warnings

[ ] Changes would cause existing functionality to not work as expected

[ ] I have added tests that prove my fix is effective or that my feature works

[ ] New and existing unit tests pass locally with my changes
opened by aparna2071 1
[Bug]: Able to delete a step that is marked as Prerequisite to another step
Is there an existing issue for this?

[X] I have searched the existing issues

What is the current behavior?

We are not showing any message to users when a step that is marked as pre-requisite to another step is deleted.

What is the expected behavior?

Show a pop with a message “Step already used as a prerequisite to #Step number, please release the step to delete“

Steps To Reproduce

Login to Testsigma account

Create a test case

Add a step 1

Add step 2 and mention step 1 as pre-requisite for step 2

Delete the Step 1

Version

Testsigma Community Edition
bug good first issue
opened by vikramvr-qa 1
fix(TestStep):"Conditional IF" step is displayed in wrong order when when we "add step"
TOS-365

Description

Fixes the wrong steps order, when we try to add a Teststep from Add step while hovering on a step

Issue

"Conditional IF" step is displayed in wrong order when we "add step" until the page is refreshed -->this occurs when cloned steps are present

Checklist:

[x] My code follows the style guidelines of this project

[x] I have performed a self-review of my own code

[ ] I have commented my code, particularly in hard-to-understand areas

[ ] I have made corresponding changes to the documentation

[x] My changes generate no new warnings

[ ] Changes would cause existing functionality to not work as expected

[ ] I have added tests that prove my fix is effective or that my feature works

[ ] New and existing unit tests pass locally with my changes
opened by manikanta-reddy-t 0
fix(Mobile Web): Not able to run mobile Web executions

here the problem is when we are saving the testdevice in a dry run config (or) in a testplan testmachine , in payload Object ''browser" should be "CHROME" but "GOOGLECHROME" is being assigned.

opened by manikanta-reddy-t 0
Getting error in testsigma agent while registering the ios simulators
Is there an existing issue for this?

[X] I have searched the existing issues

What is the current behavior?

com.testsigma.automator.exceptions.AutomatorException: Cannot run program "idb": error=2, No such file or directory at com.testsigma.automator.mobile.ios.IosDeviceCommandExecutor.runDeviceCommand(IosDeviceCommandExecutor.java:56) ~[testsigma-automator-1.0.0.jar:?] at com.testsigma.agent.mobile.ios.IosDeviceService.simulatorDeviceList(IosDeviceService.java:107) ~[agent.jar:1.3.0] at com.testsigma.agent.schedulers.IOSEmulatorScheduler.run(IOSEmulatorScheduler.java:36) ~[agent.jar:1.3.0] at jdk.internal.reflect.GeneratedMethodAccessor51.invoke(Unknown Source) ~[?:?] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?] at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:84) ~[spring-context-5.2.6.RELEASE.jar:5.2.6.RELEASE] at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) ~[spring-context-5.2.6.RELEASE.jar:5.2.6.RELEASE] at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:93) ~[spring-context-5.2.6.RELEASE.jar:5.2.6.RELEASE] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?] at java.util.concurrent.ThreadPoolExecutor$Work

Also i have added 5 android devices but agent is showing only 1 device .

Snapshot :

What is the expected behavior?

IOS Simulators should be shown on agents .

Also all the devices should be shown on the agents .

Steps To Reproduce

Start testsigma server .

Start agent for mac

Check the devices and browsers

Version

Testsigma Community Edition
bug
opened by samagarw 1