testsigmahq / testsigma Goto Github PK

Is there an existing issue for this?

• 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

Is there an existing issue for this?

• I have searched the existing issues

What would you like to add?

Surprised by the design of testsigma, but the community version has too limited functions, it can hardly be put into production, there is no team management, no project management, which is not conducive to community development

Why should this be worked on?

with basic functions

Other details

No response

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

If a test step which is marked as pre-requisite fails, then the test case execution is not proceeding to the next steps as per the configuration selected in test plan, Recovery action - > On Test Step Pre Requisite Failure -> select Report And Continue Next Step

What is the expected behavior?

The Step having prerequisite should be reported and the next step should be executed

Steps To Reproduce

1. Login to testsigma account
2. Create a test case
3. Add a step with If condition or while loop with an intent to fail
4. Create a step outside the if or while loop step and mention the above step as pre-requisite
5. Create a Test suite and this case to the suite
6. Create a Test plan and add the above test suite
7. In the test plan settings, Recovery action - > On Test Step Pre Requisite Failure -> select Report And Continue Next Step

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

On Deleting of workspace, the whole system is getting blanked unable to proceed further.

What is the expected behavior?

The app should not become unresponsive and can we switch to the default version.

Steps To Reproduce

• Create one new workspace version
• Choose it as a working version from the workspace switcher
• go to details and delete it
• Now page became blank, unable to proceed the application

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

The Operating system details shows in Browser details icon in the Test Plan under Test Lab Type

Operating system details icon is missing

What is the expected behavior?

Operating System details should display in separate icon

Steps To Reproduce

1. Create a test plan
2. And go to test plan tab
3. Check the OS details is displayed in separate icon

Version

Testsigma Community Edition

Is there an existing issue for this?

• 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

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

Refer to this bug report: https://app.birdeatsbug.com/sessions/VjOS1MjklhadEIeIoAGMRTIMwPhCDIWafsGEAm_mY_Vo

What is the expected behavior?

Refer to this bug report: https://app.birdeatsbug.com/sessions/VjOS1MjklhadEIeIoAGMRTIMwPhCDIWafsGEAm_mY_Vo

Steps To Reproduce

Refer to this bug report: https://app.birdeatsbug.com/sessions/VjOS1MjklhadEIeIoAGMRTIMwPhCDIWafsGEAm_mY_Vo

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

Doc/tutorial link

https://testsigma.com/docs/getting-started/setup/downloadable-package/

Explain the problem

On Step 2 of the above page on Windows topic point number 4
If you want to stop nginx at any point in time then, run the start_nginx.bat script

Expected should be If you want to stop nginx at any point in time then, run the stop_nginx.bat script

Your inputs to improve

Expected should be : If you want to stop nginx at any point in time then, run the _stop_nginx.bat_ script

Is there an existing issue for this?

• I have searched the existing issues

What would you like to add?

Ability to pause the Ad-hock run on desire step

Why should this be worked on?

For better debugging, if we have the option to pause the executions on desired steps we can improve the user debugging the test case by a lot.

Other details

No response

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

in the Dry Runs tab, some of the runs do not shows the browser details like below

show

What is the expected behavior?

browser details should show for all the runs

Steps To Reproduce

1. Run the tests
2. Goto Dry Runs tab
3. Check the browser details are shown for all the runs

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

getting this step: Store current Test... value into runtime varible attribute

What is the expected behavior?

should be: Store current Test... value into runtime variable attribute

Steps To Reproduce

1. Create/Open any Test Case
2. search for Store current...

Provided fix on my fork: https://github.com/creek23/testsigma

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

TestsigmaServer\ start.bat will have problem running on Windows with space on path
example, C:\Users\Home Laptop\My Testsigma Server\TestsigmaServer.start

current script will see it only as C:\Users\Home

What is the expected behavior?

script should see it as C:\Users\Home Laptop\My Testsigma Server\TestsigmaServer.start

Steps To Reproduce

To reproduce:

1. extract Community Edition on Windows with space on Path (C:\Users\Home Laptop\My Testsigma Server\)
2. run TestsigmaServer\start.bat

Provided fix on my fork: https://github.com/creek23/testsigma

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

When I run the test in Testsigma Lab its works fine, but when I run the same test in Local Devices the tests are Queued

What is the expected behavior?

Test should run successfully in local devices also

Steps To Reproduce

1. Create a test
2. Run in Local Devices
3. Test should run successfully

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

when I run script 'docker-compose up -d',
there is start testsigma two container normal and not stay starting long time.

[docker@CNT7XATST01 docker-compose-yml]$ docker-compose up -d
[+] Running 1/2
[+] Running 1/2stsigma_mysql Waiting 310.6s
⠿ Container testsigma_mysql Waiting 2749.7s
⠿ Container testsigma_server Created 0.1s

What is the expected behavior?

I expect result : it is start testsigma two container normal.
(1) mysql container is startup normal.
(2) testsigma container also is startup normal.

Steps To Reproduce

(1) OS version
[root@CNT7XATST01 ~]# uname -a
Linux CNT7XATST01 3.10.0-1160.el7.x86_64 #1 SMP Mon Oct 19 16:18:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

(2) docker version
[root@CNT7XATST01 ~]# docker --version
Docker version 20.10.17, build 100c701
[root@CNT7XATST01 ~]#
[root@CNT7XATST01 ~]# docker-compose --version
Docker Compose version v2.9.0

(3) Testsigma install by docker as below
cat > /home/app/testsigma-server/docker-compose-yml/docker-compose.yml << EOF
version: "3.9"
services:
mysql:
image: mysql:5.7
platform: linux/x86_64
container_name: testsigma_mysql
restart: always
volumes:

• /home/data/testsigma-server/db_data:/var/lib/mysql
  environment:
  MYSQL_ROOT_PASSWORD: root
  MYSQL_DATABASE: db_testsigma_opensource
  LANG: C.UTF-8
  LC_ALL: C.UTF-8
  ports:
• "3306:3306"
  command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
  healthcheck:
  test: out=$$(mysqladmin ping -h localhost -P 3306 -u root --password=root 2>&1); echo $$out | grep 'mysqld is alive' || { echo $$out; exit 1; }
  interval: 300s
  retries: 10
  testsigma_server:
  image: testsigmahq/server:v1.1.0
  container_name: testsigma_server
  ports:
• "9090:9090"
• "443:443"
  volumes:
• /home/data/testsigma-server/ts_data:/opt/app/ts_data
  depends_on:
  mysql:
  condition: service_healthy
  EOF

-- and detail steps , look below url
#79

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

After deploying the server via docker and then I navigate to UI the page displays Loading... forever

.

What is the expected behavior?

The UI shows the dashboard

Steps To Reproduce

1. Deploy using steps from here on an M1 Mac running docker using the M1 image
2. Navigate to page

Version

Testsigma Community Edition

Is there an existing issue for this?

• 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

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

there's an issue with the external editor wherein if you try to edit an element, the elements inside the create / select element box which appears on the right side disappear
it happens only sometimes though.

What is the expected behavior?

The user should be able to see the elements inside the element selector / element editor

Steps To Reproduce

Not sure what actually triggers the issue...

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

As of now we are able to create more than one test case and step group with same name in one workspace. This is causing confusion when referring to them in the list view.

What is the expected behavior?

We should not allow step group of test case with a duplicate name in the same workspace.

Steps To Reproduce

1. Create a test case with name "Test"
2. Create another test case with name "Test"

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

Invalid format of Live Workspace version in Mobile Web Application workspace

What is the expected behavior?

the workspace version format should be the same as others

Steps To Reproduce

1. Goto workspace window
2. Check the workspace version is in same format for all the workspcaes

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

There was a nested loop in the test case I wrote as a Step Group. It is supported to write nested loop while adding steps, but inside loop does not work when execute.

What is the expected behavior?

All loops working properly when run

Steps To Reproduce

In the example here, the "for" in step 1 works, but the "for" in step 1.9.2 does not.

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

Hardcoded URL local.testsigmaos.com/ui address is coming in the section of Step3: Install and configure testsigma agent

Documentation URL: https://testsigma.com/docs/getting-started/setup/docker/

What is the expected behavior?

Suggested Fix: The respective urls for testsigma agents can be listed to help users choose the URL for setting up the agent. Example:
- Open Source Version: https://localhost:portaddress/ as defined in the server section of docker-compose file
- TS Cloud Version: https://testsigma -xyz.com

Steps To Reproduce

Navigate to Step 3 on Setup using Docker section available here: https://testsigma.com/docs/getting-started/setup/docker/

Version

Testsigma Community Edition

Is there an existing issue for this?

• 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

1. Start testsigma server .
2. Start agent for mac
3. Check the devices and browsers

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

test

What is the expected behavior?

test

Steps To Reproduce

test

Version

Testsigma Community Edition

Is there an existing issue for this?

• [] I have searched the existing issues

What would you like to add?

Testsigma Community requires Postgres installation.

Why should this be worked on?

As of not to install mysql, I have the Postgres on Cloud service and we can't add an extra MySQL or MariaDB on Cloud

Postgres can be onboarded in Testsigma Community Edition software.

Other details

No response

Is there an existing issue for this?

• 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

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

So basically, I want to use this addon that says
Store test-data-1 in runtime variable test-data-2

It shows up properly over here, but when i click on record the test data values I passed just disappear...

check step 9..

What is the expected behavior?

Test-Data/$|runtime_variabled|/!|random_data_generators used with addons should be visible in the recorder.

Steps To Reproduce

1.Add any downloaded addon to your test eg [Store test-data-1 in runtime variable test-data-2]
2.Pass actual values into the addon eg [Store Hello in runtime variable $|var_text|]
3.Save the step and click on record.
4.Notice that the values that you entered into the addon have disappeared

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

test

What is the expected behavior?

test

Steps To Reproduce

test

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

When a supported browser automatically updates to a new version, it is possible to receive an error when running a test case saying the new version of the browser is not supported and only supported up to X amount.

I follow the steps here: https://support.testsigma.com/support/solutions/articles/32000021946-update-the-testsigma-agent-driver-files-manually-

However it does not appear to work. For example, My Chrome was version 97 and everything worked, however it updated to version 99. I tried to download the version 99 of the chrome driver and created a directory called 99.0 in the drivers/googlechrome and put the chrome driver in there. However it seems that the agent does not use the new version and instead is hard coded to use the driver in the 97.0 folder.

What is the expected behavior?

Based on the documentation, I should be able to create a 99.0 folder and put the 99 chrome driver in there and the agent will use the new version of the chrome driver.

Steps To Reproduce

1. Upgrade Chrome to version 99
2. Create a folder in the drivers/googlechrome folder called 99.0
3. Download the 99 chromedriver.exe and put it into the 99.0 folder
4. Run a test case using version 99 of chrome
5. You will receive an error saying that only 97 is supported.

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What would you like to add?

• Bundling mysql into the complete installation zip
• Avoid Nginx and we can serve the static assets from spring boot itself

Why should this be worked on?

1. As of not installation mysql causes lot of issues for windows users and sometimes in other os users also. Bundling it along with other components will lead to faster adoption.
2. Replacing Nginx with spring boot features will save users dealing with one more components. The lesser the no of components the faster the user can be onboarded in Testsigma Community Edition Software.

Other details

No response

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

HI Testigma Team,

Just came across your awesome open source project and wanted to get involved in your open Soruce contributions Either via code
or helping you guys test if anything comes in to my notice

Since being fan of brave browser and since it's built on chromium as same as edge

What came in to my notice is that some part of your webpage is being blocked either it maybe because of whitelabelling ar maybe due to some 3rd party blocker which happened same with facebook. even that one was reported by me and you can get a reference what might be the issue (brave/brave-browser#15629)

I am attaching a small video for reference in comparisson between brave and Edge Browser
Please do take a look and forgive me in advance if it's mistake from my side.

Brave Browser Result

Edge Browser Result

What is the expected behavior?

Expected Result
Name and Input url are hidden / blocked by the browser as compared to edge it's visible on Edge

Solution
Please create a issue on Brave to Either whitelabel your product or get assistanc from them

Steps To Reproduce

Download Brave Browser
Click on create test case
Inputs are hidden / blocked by brave browser

Version

Testsigma Cloud

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

Test Lab Type details are missing in the Run Results Details window

What is the expected behavior?

Test Lab Type details should be displayed

Steps To Reproduce

1. Create a test plan
2. Run the test
3. Check the Test Lab Type details are shown in the Run Results Details

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

Doc/tutorial link

https://testsigma.com/docs/test-data/types

Explain the problem

The help link for data types(https://testsigma.com/docs/test-data/types) in test steps seems invalid.

Your inputs to improve

The correct link should be pointed to https://testsigma.com/docs/test-data/types/overview/

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

The Test Plan descriptions are collapsed in the Run Results window like below

What is the expected behavior?

The complete descriptions should be displayed clearly

Steps To Reproduce

1. Create a Test Plan with some good lines of descriptions
2. Run the Test Plan
3. Go to the Run Results window and check the Description is looks good and clear

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

Doc/tutorial link

No response

Explain the problem

We want to deploy this on K8s cluster . Can you please provide some documentation for this ?

Your inputs to improve

We have doc for docker deployment but not for K8s . Can you please create 1 and share it . It will help people who want to use it on clusters and test it .

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

The web interface listens only to HTTPS at 443

What is the expected behavior?

In many enterprise deployments SSL termination is usually done at a reverse proxy - nginx notably, and also there the real URL is configured. Testsigma should expose a plain HTTP listener, and should not try to guess what the URL of the server is, but rather expose it as a configurable env var.

Steps To Reproduce

1. Installation.

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

test

What is the expected behavior?

test

Steps To Reproduce

test

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

The service deployed on Linux has installed google browser on Linux. The execution times are incorrect.

Unable to create a new Test Session due to unexpected failure(0x537). Please contact Support for more details. - unknown error: Chrome failed to start: exited abnormally. (unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.) Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03' System info: host: 'program', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-1160.24.1.el7.x86_64', java.version: '11.0.14.1' Driver info: driver.version: TestsigmaDriver remote stacktrace: #0 0x559f5d54d303 #1 0x559f5d321d37 #2 0x559f5d34a157 #3 0x559f5d346330 #4 0x559f5d3874a6 #5 0x559f5d37e753 #6 0x559f5d351a14 #7 0x559f5d352b7e #8 0x559f5d59c32e #9 0x559f5d59fc0e #10 0x559f5d582610 #11 0x559f5d5a0c23 ...

What is the expected behavior?

Hope to be normal

Steps To Reproduce

1.Recording procedure
2.Run test

Version

Testsigma Community Edition

Is there an existing issue for this?

• 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

1. Login to Testsigma account
2. Create a test case
3. Add a step 1
4. Add step 2 and mention step 1 as pre-requisite for step 2
5. Delete the Step 1

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What would you like to add?

There are two types of NLPs that are available in Testsigma to capture value from a field.

• Store text from the field
• Store value from the field

What's the problem (As described by Amit on Discord):

Sometime during automation, we tend to presume that the data entered in fields are in form of text but in this case, the data that we are entering in the particular field is going to a placeholder / is in form of a value. So there we need to use a different NLP i.e - Store value from the field instead of storing the text.

Basically, in terms of selenium when we use Store text NLP it uses the - element.getText()
which is empty here, rather when we use to store value NLP that simply means --- element.getAttribute("value")
which returns the actual value which appears to be as text.

Reference video of Issue that I encountered: https://app.birdeatsbug.com/sessions/1oyjn7qy_ZcbCY13OGqQOBuWr1IK82wbF02r-fTkACtL

Reference video of the cause behind this issue: https://watch.screencastify.com/v/8jMX6FuELuwnN8x8edOg

Why should this be worked on?

Ideally, Low code users (assume a BA, or PO) do not need to know about all this finer nasty stuff that usually selenium programmers learn as the intent of the tool is to allow users to author using NLP.

This can be auto-computed if the value is "".

We can also give some triggers for Smart AI that can enable all these special features. This can add to a new kind of feature to testsigma. I am open to discuss more on this.

Other details

"Loud thinking: What could be the bad consequence of this?" Do you see any?

Is there an existing issue for this?

• I have searched the existing issues

What would you like to add?

There should be feasibility to run the tests on private selenium grids

Run-on Custom Grid option has to be provided where they can provide their URL and run

Why should this be worked on?

This has been there on many other tools like Testim, mabl etc.,.Since we want to have our own test infrastructure similar to us there are numerous who would spin their grids. So to support I would request to add this capability

Other details

No response

Is there an existing issue for this?

• 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

1. Download the testsigma bundle
2. Install the MySql
3. Setup the env variable for MYSQL_PASSWORD
4. Start the Nginx
5. And Start the server then start the Agent

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

An error message shows success but the condition shows false.
There was this issue where the condition was correct but still it was failing for some reason,
The condition was if the url that I have provided starts with the given test-data if yes then it should execute a certain number of steps.
Even the error message says that: "The TestData starts with the expected value"

What is the expected behavior?

If the condition is true then the test steps passed inside the if condition should be executed

Steps To Reproduce

1.Open any webpage with a long url.eg [https://www.amazon.in/s?k=iphone&crid=LRYXLYA4RQN8&sprefix=iphone%2Caps%2C230&ref=nb_sb_noss_1]

2.Add an if condition [If current url [starts with] https://www.amazon.in]
2.1 Perform certain action

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

When a workspace version is copied the test suites to be missing in the new version and also in test plan list view some additional adhoc run related information seems to shown which is not there in the original version.

What is the expected behavior?

The version copy should also copy test suites. And apart from test plan no other information related to adhoc runs should be shown.

Steps To Reproduce

1. navigate workspace settings
2. Select version list view
3. Click on "Copy version" button
4. Provide the new name for the new version and submit
5. select the workspace switcher and select the new version which is copied
6. Navigate to test suites list view in the new version copied and we can notice none of the test suites are copied
7. Navigate to test plan list view and you can notice apart from the test plans in the older version there are additional entries related to adhoc runs (assuming we have executed few adhoc runs for any test case).

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

when we select the Local Devices to run options in ad-hoc runner, the Browser Name is not shown sometimes

What is the expected behavior?

the browser name should be displayed

Steps To Reproduce

1. Launch the ad-hoc runner tab
2. Select the Local Devices tab
3. Check the browser name display properly

Version

Testsigma Community Edition

Is there an existing issue for this?

• I have searched the existing issues

What would you like to add?

Add docker-compose.yml file to the release artifacts.

Why should this be worked on?

• It's a server setup file that can be given as a release output.
• Currently, it is available in the source code folders. For pure consumers of testsigma, it is feasible to provide all setup documents in the release package only.
• Binding the docker-compose file to the release would also enable introducing breaking changes in the future. As of today, the docker compose file is coupled with the released versions (current as well as previous).

Other details

Priority (from user perspective): Minor

Is there an existing issue for this?

• I have searched the existing issues

What would you like to add?

test

Why should this be worked on?

test

Other details

test

Is there an existing issue for this?

• I have searched the existing issues

What would you like to add?

Show page source for failed step.

Why should this be worked on?

Having a screenshot alone is not enough for debugging failed steps, We can have a page source of that moment so alongside the screenshot. This will improve the failed step debugging by a large margin.

Other details

No response

Is there an existing issue for this?

• I have searched the existing issues

What would you like to add?

Refer to the report here: https://app.birdeatsbug.com/sessions/IbJfHLnCHNBI7KFOR9dwBENj27znIaa9s8w4_tbbqxM3

Why should this be worked on?

It will improve the Usability & Script Authoring Experience

Other details

NA

Is there an existing issue for this?

• I have searched the existing issues

What is the current behavior?

on the ad-hoc runner window the Browser Version shows as 1 for Edge in Local Devices options

whereas in the Testsigma Lab has the right listed Browser Version as below

What is the expected behavior?

the browser version should same as Testsigma Lab configuration in Local Devices as well

Steps To Reproduce

1. Create the test case in testsigma
2. Go for the Ad-hoc run tab
3. Select the Local Devices tab
4. Confirm the Edge browser version displays the same as Testsigma Labs

Version

Testsigma Community Edition

Discussed in #20