testspace-com / support

Support for bugs and feature requests

Testspace Support

Support for bugs and feature requests

Testspace is an integrated test solution built for DevOps.

Documentation

Documentation for Testspace can be found at https://help.testspace.com.

support's Issues

Unable to setup a account via Marketplace

Discussed in #19

^{Originally posted by rfennell August 25, 2021}
I have tried to set up a personal free account on my GitHub personal account. I was able to add Testspace via the marketplace but the call back to Testspace.com to complete the process failed

Not sure what I should do now as it appears the testspace.com account has not been fully created. I seem to be able to sign in but only the samples are shown, there is no add new project.

What should I do to resolve this?

Allow onboarding users to choose their preferred GitHub email

When onboarding on TestSpace by "Sign up with Github" option, the user can't choose their preferred GitHub email to be connected to TestSpace, the "primary" GitHub email is selected by default and can not be changed during onboarding.

Once the account has been created, the email can be updated in TestSpace by "Edit Profile". The emails gets updated correctly, but after a while, probably after some "sync with GH" job runs, the emails gets reverted to the GH "Primary" email.

That's been an issue for me when onboarding, as my "Primary" GH email is my personal one, but I'd like to choose my work email as the one to be linked to TestSpace. Currently I'm getting work-related (from TestSpace) emails to my personal email, instead of to my work email.

Check Run used for Publishing Test Results

For Testspace Connected projects publishing results, a new check run will be created.

• The content of the check run will be based on the current Testspace Results email
• A limited number of test failures will be captured in the check run's annotations
• A link to Testspace for detailed information will be provided

Testspace client support for `@`, `->`, etc. "exotic" characters in branch names

The client is not handling branch names with unique characters.

Reference example - https://github.com/munderseth/testspace.getting-started/tree/update/babel-eslint-%3E%40babel-eslint-parser.

Setup erroring out - https://github.com/munderseth/testspace.getting-started/runs/2906773581?check_suite_focus=true

A couple of suggestions

Hi, Mark :)

So here are my two questions/suggestions:

1. Is there a way to rename the badge, that is generated from each test ? It currently says "test" and I would like it to say for example "TestSpace" or "TestSpace internals" etc.

2. Is there any way currently to enable integration of the TestSpace stats and graphs, inside GitHub ? i.e. there is a label that appears on a PR and a link "details" next to it, which leads to the TestSpace website. Instead, the link to open a page inside GitHub, which to show overviews of stats and graphs, and for more details to have a link to the space inside TestSpace website.

P.S. I just found out that in the GitHub marketplace, under Actions, if I search for "testspace", nothing comes up.

Document the difference between --build-status failure vs error

Documentation on this page should state the difference between failure and error when used with the --build-status option. It is not clear when a build would have an error status instead of a failure status.

https://help.testspace.com/docs/reference/testspace-client

documentation error: Publish > Tools Support > Python

https://help.testspace.com/publish/tools-support-python#pytest

You have:

pytest --junitxml=results.xml

Should be:

pytest --junit-xml=results.xml

Trial signup uses prior email without ability to edit

Steps:

1. Sign up for free Open account, when account setup is complete, log out etc.
2. In same browser, sign up for Team account (I'm using Chrome on Linux)
   
3. The dialog prompting for a domain name and email address use the email specified in (1). The email is grayed out and cannot be edited.
4. Open a different browser (Firefox) and do step (2). Email address is blank and can be edited.

Suggests that browser has saved state and this data is being used to set the email.

Option to suppress failure on skipped suites

We are currently having test run failures in our Github PRs, because we skip suites under certain conditions, in order to be smart about our CI servers load. We for instance skip backend tests, if there haven't been any backend changes.

This is reported as failure by testspace to Github and makes the PRs look like specs are failing.

It would be great to have a configuration option to ignore deviations in test count.

Doc: Incremental how link broken

The how link on the bottom of this page...

https://help.testspace.com/docs/publish/push-data-results#incremental

... results in a 404 attempting to resolve:

https://help.testspace.com/docs/publish/push-data-client#url