add basic e2e tests for stack title#4206
Conversation
Signed-off-by: Simon Hötten <s+git@hoetten.org>
Signed-off-by: Simon Hötten <s+git@hoetten.org>
Signed-off-by: Simon Hötten <s+git@hoetten.org>
Signed-off-by: Simon Hötten <s+git@hoetten.org>
829693b to
2be2afb
Compare
Yes, fully agreed that the current setup is far from perfect. Thanks for adding the tests nevertheless and for your input.
Yes, that is something that might need a general approach for nextcloud cypress tests. It would be quite helpful to also be able to pre-seed data with that.
We may want to move over to the https://github.com/nextcloud/nextcloud-cypress helpers here as well as they at least speed up test setup in terms of login and session handling. I took the liberty to rebase so we can get this merged. |
Signed-off-by: Julius Härtl <jus@bitgrid.net>
7f84dda to
5958632
Compare
Summary
I created some basic e2e tests for stack title editing & aborting it.
Some things to consider:
To be honest i'm not inclined to write any more tests for now, because i think the cypress setup needs some work upfront first (and also other things are more fun ;)). My two main concerns are that
a) the dev and test database is shared and tests don't clean up after themselves and
b) tests run really slow, mostly through how the setup / spec bringup is handled (my machine already takes >5min, for a tiny amount of tests)
Or am i just missing something here?
Checklist