Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot get the test array's browser or projectName to consistently populate when test.describe() is used #143

Open
5 of 10 tasks
john-cyndx opened this issue Oct 28, 2022 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers
Milestone

Comments

@john-cyndx
Copy link

Description

summaryResults.tests[i].browser and summaryResults.tests[i].projectName are only populated when the suiteName for a test is the path of the test. when test.describe() is used and the suiteName is given, the browser and projectName are empty strings.

What type of issue is this? (place an x in one of the [ ])

  • bug
  • enhancement (feature request)
  • question
  • documentation related
  • example code related
  • testing related
  • discussion

Requirements (place an x in each of the [ ])

  • I've read and understood the Contributing guidelines and have done my best effort to follow them.
  • I've read and agree to the Code of Conduct.
  • I've searched for any related issues and avoided creating a duplicate issue.

Bug Report

Filling out the following details about bugs will help us solve your issue sooner.

Reproducible in:

package version: 1.23.0

node version: 16.x

OS version(s): n/a

Steps to reproduce:

  1. A test with the line test.describe('[some test suite title]')
  2. Run the test on any browser or project
  3. Browser and projectName will be blank for that test

Expected result:

Browser and projectName to be populated

Actual result:

Browser and projectName are empty strings in the test array object

@seratch seratch added enhancement New feature or request good first issue Good for newcomers labels Oct 31, 2022
@seratch seratch added this to the 1.x milestone Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants