-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
tests: Write end-to-end tests #150
Labels
Comments
pawamoy
added
tests
Issue or enhancement within tests
top-priority
Absolute priority
labels
Apr 20, 2024
You can take a look here https://github.com/15r10nk/lazy-imports-lite/blob/main/tests%2Ftest_exec.py where I do end to end tests. Just to get some inspiration. There are a lot of ways to use inline-snapshot. I'm curious how you will use it. |
pawamoy
added a commit
that referenced
this issue
Dec 23, 2024
pawamoy
added a commit
that referenced
this issue
Dec 23, 2024
pawamoy
added a commit
that referenced
this issue
Dec 23, 2024
pawamoy
added a commit
that referenced
this issue
Dec 23, 2024
pawamoy
added a commit
that referenced
this issue
Dec 23, 2024
pawamoy
added a commit
that referenced
this issue
Dec 24, 2024
pawamoy
added a commit
that referenced
this issue
Dec 24, 2024
pawamoy
added a commit
that referenced
this issue
Dec 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With our growing number of rendering options, it is hard to make sure that changes to templates do not cause regressions. We should add end-to-end tests for all combinations of rendering options (matrix), with simple input, asserting the output stays unchanged on next runs. We could maybe use pytest inline snapshot from @15r10nk for that 😉
The text was updated successfully, but these errors were encountered: