-
Notifications
You must be signed in to change notification settings - Fork 145
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
[QA] VizroAI UI tests #882
base: main
Are you sure you want to change the base?
Conversation
for more information, see https://pre-commit.ci
…onent_library_tests
for more information, see https://pre-commit.ci
View the example dashboards of the current commit live on PyCafe ☕ 🚀Updated on: 2024-12-12 12:42:53 UTC Link: vizro-core/examples/dev/ Link: vizro-core/examples/scratch_dev |
…o_ai_ui_tests � Conflicts: � .github/workflows/vizro-qa-tests-trigger.yml � vizro-core/hatch.toml
for more information, see https://pre-commit.ci
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @l0uden , added a few comments
@@ -48,6 +48,7 @@ prep-release = [ | |||
] | |||
pypath = "hatch run python -c 'import sys; print(sys.executable)'" | |||
test = "pytest tests {args}" | |||
test-e2e-vizro-ai-ui = "pytest -vs --reruns 1 tests/e2e/test_vizro_ai_ui.py --headless {args}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we add this as a hatch script, does it run locally if I was to use that command?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, anyway to use it you need to run the VIzroAI UI first
@@ -56,6 +57,7 @@ test-unit-coverage = [ | |||
"- coverage combine", | |||
"coverage report" | |||
] | |||
vizro-ai-ui = "python examples/dashboard_ui/app.py &" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this hatch command really necessary? Could this not work like the other examples in vizro-core
where the user can specify the example by providing args
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couldn't do it. Let's take a look a this way together
vizro-ai/pyproject.toml
Outdated
] | ||
norecursedirs = ["tests/tests_utils"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does that do?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wanted to do it as in vizro-core repo, but looks like here it doesn't have any sense. Thanks. Deleted
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it might be better to have a test_utils also per folder, like here for e2e? Then you could save yourself also all the e2e file prefixes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My point was to make same folder structure as in vizro-core for the tests.
@@ -0,0 +1,204 @@ | |||
#!/usr/bin/env bash | |||
|
|||
#The MIT License (MIT) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we have a license here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I took this file from the repo which has MIT license, in this case we should specify it.
Description
Moved VizroAI UI tests from vizro-qa
Notice
I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":