-
Notifications
You must be signed in to change notification settings - Fork 167
Add simple test demo for integration testing #663
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
Conversation
ab61775 to
280221c
Compare
1f39a0a to
6f58feb
Compare
jing-chen1
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use '' for all strings instead of "", React.FC instead of FC and move the import from react to the top
devalevenkatesh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome work!
| > | ||
| <AudioInputControl /> | ||
| <VideoInputControl /> | ||
| <AudioOutputControl /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just wonder do we need audio output here, does it change any attendee states?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't need it for roster test. But since this is a MeetingControls container, I think it's good to keep it. How do you think?
Issue #:
React Component Library is lack of integration testing coverage.
Description of changes:
Create a simple demo App under
/integrationfolder.This simple demo has a main page which serves as a menu. We could reuse the component and container to quickly build a simple test demo according to testing requirement. This menu could redirects the App to the specific test demo to do the testing.
Some screenshots for review
Home
Roster Test App - Before Joining
Roster Test App - After Joining
Testing
Have you successfully run
npm run build:releaselocally?Yes
How did you test these changes?
Try the basic e2e testing and make sure the demo works well.
If you made changes to the component library, have you provided corresponding documentation changes?
Yes, in CHANGELOG. And create a simple README to guide on adding new test demo.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.