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

🐞 [Bug]: Adapt selenium workflow to take env as a variable in manual trigger for a run and better visual add test report #3755

Open
1 task done
ramezsaeed opened this issue Dec 16, 2024 · 0 comments
Labels
type_bug Something isn't working
Milestone

Comments

@ramezsaeed
Copy link
Contributor

ramezsaeed commented Dec 16, 2024

Is there an existing issue for this?

  • I have searched the existing issues

which package/s did you face the problem with?

Dashboard

What happened?

Step1

The selenium workflow test is running always to deploy a local dashboard.
this should be updated to also pass the env as a variable to be able to trigger it manually on different environments; the same like we do in grid nightly test workflow.

  • dev (statging)
  • qa
  • test
  • main

Screenshot from 2024-12-16 16-04-52

Step2

Add a better test report view by adding package "pytest-html" in the requirements file.
and trigger the testrun with flag "--html=report.html"

to have a similar view to grid client test workflow.

Screenshot from 2024-12-16 16-11-37

image

which network/s did you face the problem on?

Dev, QA, Test, Main

Relevant log output

--
@ramezsaeed ramezsaeed added the type_bug Something isn't working label Dec 16, 2024
@ramezsaeed ramezsaeed changed the title 🐞 [Bug]: adapt selenium workflow to take env as a variable in manual trigger for a run 🐞 [Bug]: Adapt selenium workflow to take env as a variable in manual trigger for a run Dec 16, 2024
@ramezsaeed ramezsaeed changed the title 🐞 [Bug]: Adapt selenium workflow to take env as a variable in manual trigger for a run 🐞 [Bug]: Adapt selenium workflow to take env as a variable in manual trigger for a run and better visual add test report Dec 16, 2024
@ramezsaeed ramezsaeed added this to the 2.7.0 milestone Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type_bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant