(WIP 93)Test Case of Time function #94
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yashb196
approved these changes
Nov 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Through last week's efforts, the time function has been repaired and the time can now be displayed and set. The manual test has been passed, and the framework service through moxios has been added to simulate whether the simulator can work normally after pressing the save button.Below are the steps I intend to test in the test simulator framework.
In the test case, we need to make sure it is correct before setting it. (Display time, and button is used to modify time)
2.
After clicking the modification time, we can make changes and save them.
3.After clicking the save button, we should return the set time and return to the normal value
The time test has been completed, and a test about tagwindow has been added.