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

Use LiveServerTestCase for frontend tests #1854

Open
niklasmohrin opened this issue Jan 23, 2023 · 0 comments · May be fixed by #2077
Open

Use LiveServerTestCase for frontend tests #1854

niklasmohrin opened this issue Jan 23, 2023 · 0 comments · May be fixed by #2077
Assignees
Labels
Attempt This might turn out to be not (easily) implementable. In this case we'll probably close the issue. [C] Tests and CI New or better testing and CI [P] Minor Minor priority [T] Refactoring Existing parts should become faster, more readable, or in any other way better.

Comments

@niklasmohrin
Copy link
Member

With our current setup for frontend tests, we generate static html files that are then opened with selenium by a nodejs script. This comes with the disadvantage, that we cannot (in all cases) test the behavior when submitting forms, which is something we want to do more often. There is https://docs.djangoproject.com/en/4.1/topics/testing/tools/#liveservertestcase which could be used as a driver for the frontend tests. Even further, it turns out the linked documentation even provides an example of a selenium driven test, so we should investigate porting our frontend tests to Python.

@niklasmohrin niklasmohrin added [P] Minor Minor priority [C] Tests and CI New or better testing and CI [T] Refactoring Existing parts should become faster, more readable, or in any other way better. labels Jan 23, 2023
@janno42 janno42 added the Discussion This issue requires some discussion and a decision what a solution might look like. label May 15, 2023
@niklasmohrin niklasmohrin changed the title Investigate using LiveServerTestCase for frontend tests Use LiveServerTestCase for frontend tests May 15, 2023
@janno42 janno42 added Attempt This might turn out to be not (easily) implementable. In this case we'll probably close the issue. and removed Discussion This issue requires some discussion and a decision what a solution might look like. labels May 15, 2023
@hansegucker hansegucker linked a pull request Nov 20, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Attempt This might turn out to be not (easily) implementable. In this case we'll probably close the issue. [C] Tests and CI New or better testing and CI [P] Minor Minor priority [T] Refactoring Existing parts should become faster, more readable, or in any other way better.
Development

Successfully merging a pull request may close this issue.

3 participants