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

Bar: Convert Protractor Tests to Puppeteer #5838

Closed
ericangeles opened this issue Nov 10, 2021 · 1 comment · Fixed by #6189
Closed

Bar: Convert Protractor Tests to Puppeteer #5838

ericangeles opened this issue Nov 10, 2021 · 1 comment · Fixed by #6189
Assignees
Labels
for: dev type: unit testing [3] Velocity rating (Fibonacci)

Comments

@ericangeles
Copy link
Contributor

ericangeles commented Nov 10, 2021

Is your feature request related to a problem or use case? Please describe.
Convert bar component tests to puppeteer.

Describe the solution you'd like
Convert all tests scenarios in protractor to puppeteer. For the naming can be, {component}.puppeteer-spec.js

Describe alternatives you've considered
N/A

@ericangeles ericangeles added [3] Velocity rating (Fibonacci) type: unit testing for: dev labels Nov 10, 2021
@davidcarlsonberg davidcarlsonberg self-assigned this Mar 7, 2022
@davidcarlsonberg davidcarlsonberg moved this from To do to In progress in Enterprise 4.62.x (Mar 2022) Sprint Mar 7, 2022
@davidcarlsonberg davidcarlsonberg moved this from In progress to Pending Review in Enterprise 4.62.x (Mar 2022) Sprint Mar 10, 2022
@ericangeles ericangeles moved this from Pending Review to Ready for QA (beta) in Enterprise 4.62.x (Mar 2022) Sprint Mar 21, 2022
@CindyMercadoReyes
Copy link
Collaborator

This task is now completed

@CindyMercadoReyes CindyMercadoReyes moved this from Ready for QA (beta) to Done in Enterprise 4.62.x (Mar 2022) Sprint Mar 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: dev type: unit testing [3] Velocity rating (Fibonacci)
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

3 participants