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.

Sign up for GitHub

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

Jump to bottom

Define DSL structure to cover recurring functionalities in e2e tests #8

Open
3 tasks
Tracked by #5
turnerrainer opened this issue Oct 28, 2024 · 0 comments
Open
3 tasks
Tracked by #5

Define DSL structure to cover recurring functionalities in e2e tests #8

turnerrainer opened this issue Oct 28, 2024 · 0 comments
Assignees
@Danwerk @T4NKER
Labels
e2e test feature TDD v2.0.2

Comments

@turnerrainer
Copy link
Collaborator

turnerrainer commented Oct 28, 2024 •
edited
Loading

Note

This is a sub-issue of #5

AS AN Architect
I WANT TO use DSL to cover recurring functionalities in e2e tests
SO THAT generating these tests could be automated instead of writing them manually

Acceptance Criteria

  • DSL for e2e tests are generic in regard of e2e automated test frameworks

E.g. Playwright
@turnerrainer turnerrainer mentioned this issue Oct 28, 2024
Open
5 tasks
@turnerrainer turnerrainer moved this to In Progress in Bürokratt Sprint Oct 28, 2024
@turnerrainer turnerrainer added this to the v1.0.0 milestone Oct 28, 2024
This was referenced Oct 28, 2024
Open
Open
@rasmusei rasmusei moved this from In Progress to Backlog in Bürokratt Sprint Feb 3, 2025
@rasmusei rasmusei removed this from the v1.0.0 milestone Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Danwerk Danwerk

@T4NKER T4NKER

Labels
e2e test feature TDD v2.0.2
Projects
Bürokratt Sprint
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Danwerk @turnerrainer @rasmusei @T4NKER