-
Notifications
You must be signed in to change notification settings - Fork 2
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
Test components #42
Test components #42
Conversation
johncalesp
commented
Feb 17, 2023
- Unit test for main sections of the UI and utils.js
- Made small changed on the styling of local GPU.
…| PerfBarContainer
expect(root).toBeTruthy(); | ||
}); | ||
}); | ||
test("Render App correctly, it must show begin analysis button", () => { |
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.
The comment isn't necessarily true as it will be disconnected.
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.
Changed the comment and testing title
render(<App />); | ||
// For testing there is no default socket connection. It will show the warning screen | ||
|
||
expect(screen.getByText(/connection has been lost to the profiler. please reconnect the profiler and double check your ports then click connect/i)).toBeTruthy(); |
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.
I would just double check if the App renders something instead of relying on a string. That seems very brittle
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.
added reconnect button to the test