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

feat(tests): add integration test #282

Closed
3 tasks done
dargmuesli opened this issue Jun 5, 2021 · 2 comments
Closed
3 tasks done

feat(tests): add integration test #282

dargmuesli opened this issue Jun 5, 2021 · 2 comments
Assignees
Labels
feature New feature or request hacktoberfest Recommendation for work that qualifies for hacktoberfest approvals technical Not a feature nor a bug

Comments

@dargmuesli
Copy link
Member

dargmuesli commented Jun 5, 2021

  • evaluate cypress

    • cypress is now part of the alpha branch! 📢
    • you can open cypress by running the pnpm cypress:open script inside the nuxt directory 🚀
    • the cypress configuration is located at nuxt/cypress 👀
  • create e2e (end to end) tests that check if all pages render correctly 🏁

    • currently there is one example test here
    • the example test does not necessarily include the best way to check if a page renders correctly, maybe a check for http status code 200 is enough first ☝
    • many pages require a login to be accessed and the cypress docs give a description on how to handle login in e2e tests here! 📔
    • as cypress is part of the nuxt/vue 3 migration, pages will most likely not function right now... the tests that are to be written are exactly the ones that check for that! It's ok for them to fail right now, which gives reason for the issues to be fixed in another task. 🚨
  • create proper e2e tests, including the database as the cypress docs describe in their testing strategies section 💯

    • either mock the database response or start the maevsi_stack before testing 💁
    • remember that the CI runs fully inside Docker, which makes it hard to start a Docker stack inside it... the challenge of this task is to figure out how to make the stack available and let the tests run on it even inside the CI 🧑‍💻🤓
    • create breadcrumb tests as started in a8ee2a2 🍞

    Moved to test(e2e): complete integration tests #909.

@dargmuesli dargmuesli added the feature New feature or request label Jun 5, 2021
@dargmuesli dargmuesli added this to To do in Intermediate via automation Jun 5, 2021
@dargmuesli dargmuesli added the technical Not a feature nor a bug label Jun 16, 2021
dargmuesli added a commit that referenced this issue Oct 11, 2022
@azolus
Copy link
Contributor

azolus commented Oct 15, 2022

I'll give it a go 🤞🏼

@dargmuesli dargmuesli added the hacktoberfest Recommendation for work that qualifies for hacktoberfest approvals label Oct 17, 2022
@dargmuesli dargmuesli moved this from To do to In progress in Intermediate Nov 2, 2022
@dargmuesli
Copy link
Member Author

Thank you for your contribution of the second task! I'll take over the third.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request hacktoberfest Recommendation for work that qualifies for hacktoberfest approvals technical Not a feature nor a bug
Projects
Archived in project
Intermediate
  
In progress
Development

No branches or pull requests

2 participants