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

Richard/acceptanceTests #153

Merged
merged 45 commits into from
Oct 20, 2021
Merged

Richard/acceptanceTests #153

merged 45 commits into from
Oct 20, 2021

Conversation

chomosuke
Copy link
Owner

Some optional step I did not do. If @waltervan00 think any of them are important to do just tell me or branch out from this branch.

Shang Zhe Lee and others added 30 commits October 8, 2021 20:29
Add support for multiple API route pattern handlers.
@chomosuke chomosuke added the enhancement New feature or request label Oct 19, 2021
@chomosuke chomosuke added this to the Sprint 3 milestone Oct 19, 2021
@chomosuke chomosuke self-assigned this Oct 19, 2021
@chomosuke chomosuke added this to Sprint 3 in Product backlog via automation Oct 19, 2021
@chomosuke chomosuke added this to In progress in Sprint 3 via automation Oct 19, 2021
Sprint 3 automation moved this from In progress to Reviewer approved Oct 20, 2021
Copy link
Collaborator

@shangzhel shangzhel left a comment

Choose a reason for hiding this comment

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

I am technically opposed to the usage of ids in the React elements because it means the component becomes unsuitable for reuse. However our project is complete and where will not be a case for us to reuse the components so it is a non-issue. Approved.

@chomosuke
Copy link
Owner Author

I am technically opposed to the usage of ids in the React elements because it means the component becomes unsuitable for reuse. However our project is complete and where will not be a case for us to reuse the components so it is a non-issue. Approved.

Out of curiosity, do you think using the css selector with class name as I've done before 68b3037 would be better?

@chomosuke chomosuke merged commit 93c91a6 into master Oct 20, 2021
Sprint 3 automation moved this from Reviewer approved to Done Oct 20, 2021
Product backlog automation moved this from Sprint 3 to Sprint 3 Done Oct 20, 2021
@chomosuke chomosuke deleted the richard/acceptance-tests branch October 20, 2021 05:31
@shangzhel
Copy link
Collaborator

Generic selectors like button and text that rely on user-visible elements would be preferred over selecting by implementation details like class names and ids. That way the acceptance tests would execute as if it were a human controlling the browser by observing and interacting with visible elements.

@chomosuke
Copy link
Owner Author

I see

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Product backlog
  
Sprint 3 Done
Development

Successfully merging this pull request may close these issues.

None yet

3 participants