-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add tests for existing functionality #134
Comments
@nazmulidris willing to help |
@0xkelvin Thank you. Here is a good place to get started to get a handle on terminals and TUIs: https://github.com/r3bl-org/onboarding In the current tuify codebase we have tests in the following files:
There need to more tests to check things that a user would perform, such as try and select a single item. There's the happy path. Where they have a few items and enough display viewport size to see them all without scrolling. Then they make their selection or not, and we are done.
You can see in some tests the following trait is mocked https://github.com/r3bl-org/r3bl_rs_utils/blob/main/tuify/src/components/select_component.rs#L26 so that you can check what its contents are (very similar to ReactJS snapshot tests). In these cases, it is important to override the color support, since we run all tests in CI/CD and they don't all support color output. This is done in one of the tests listed above. Here are all the paths that I've been manually testing: It would be great to automate those testing paths. PLMK if you have any questions 👍🏽 . And we have a discord server if you would like to chat (more sync than async like issues) about the issue or PR. |
tuify
folderThe text was updated successfully, but these errors were encountered: