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: code coverage with playwright #90

Merged
merged 27 commits into from
Mar 3, 2024
Merged

feat: code coverage with playwright #90

merged 27 commits into from
Mar 3, 2024

Conversation

jwala-anirudh
Copy link
Collaborator

Addressing our long standing issue #43 we add the following changes.

  • playwright testing framework setup with configuration
  • e2e test server setup with ability to seed data for:
    • chat-app
    • ecommerce
    • generated-credentials
    • social-media
    • todo
  • added test coverage for todos, healthcheck
  • added testing contribution guidelines

Contributor: @shrey-dadhaniya

jwala-anirudh and others added 22 commits January 21, 2024 12:57
feat: add test cases for health check and  todo app
@wajeshubham
Copy link
Collaborator

@jwala-anirudh There are some conflicts in this branch. Please resolve whenever you are free. Thanks! :-D

Copy link
Collaborator

@wajeshubham wajeshubham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jwala-anirudh Thanks for the PR! PR looks good apart from some minor changes to be done. Also, can we add steps to test our app in README.md similar to installation instructions? That would be great.

### Folder Structure:

```
$ROOT_FOLDER/e2e/{package}/{module}/{file-indicator}.test.js
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can add folders that are standardise by default with .gitkeep included, giving user freedom to only create {file-indicator}.test.js and nothing else.

You can refer to our frontend example folder for this (I understand that we have some preconfigured test files in e2e folder but we can predefined nested folders based on packages and modules) and we can create predefined folders for each package and module with .gitkeep file in it to avoid inconsistent packages and modules being injected by contributors.

Would love to hear from you about this approach @jwala-anirudh

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only reason behind this was to keep the e2e folder structure same as src as close as possible in order to understand to which file exactly the test case is being added to.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jwala-anirudh Thanks for the clarification. We will review the folder structure thoroughly to keep our e2e tests consistent before merging.

Copy link
Collaborator

@wajeshubham wajeshubham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍🏼. Thanks @jwala-anirudh @shrey-dadhaniya

@wajeshubham wajeshubham merged commit 79541d5 into main Mar 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request testing
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants