-
Notifications
You must be signed in to change notification settings - Fork 166
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
docs: Test cases for core and PQM. #1870
base: main-doc-test-case-struct
Are you sure you want to change the base?
Conversation
e807b78
to
c4d95eb
Compare
c4d95eb
to
7b1ff75
Compare
5ff7d90
to
24c97b1
Compare
7b1ff75
to
48c4560
Compare
Signed-off-by: andreidanila1 <[email protected]>
48c4560
to
f2f67a6
Compare
The tests cover: home page, add page, connection flow, emu and device interaction. Signed-off-by: andreidanila1 <[email protected]>
The tests cover all the PQM instruments. Signed-off-by: andreidanila1 <[email protected]>
f2f67a6
to
19fb654
Compare
|
||
**Result:** PASS/FAIL | ||
|
||
.. _tst-add-verify: |
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.
is this intended?
4. Write "M3k". | ||
5. Press enter. | ||
|
||
Expected result: The device name changes both in the device browser and in the tool menu. |
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.
indentation issues
4. Possible steps. | ||
1. Close the "Oscilloscope" window. | ||
- **Expected result:** The "Oscilloscope" tool is reintegrated into the main window. | ||
2. Close the application. |
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 rephrase this and add 2 more steps here. The tester shouldn't choose from 2 possible scenarios. The test should have a single result (pass or fail).
I would go the following way:
4. close the osc window + expected result
5. detach it again without an expected result
6. close the application + expected result
It would also integrate better with the following test.
**Steps:** | ||
1. Click on the **Rms** tool. | ||
2. Observe the application's behavior. | ||
- **Expected result:** In the top section of the tool widget, there is an Info button, a PQEvents indicator, a Run button, a Single button, and a Settings button. The Settings menu is open, and the Settings button is in a checked state. In the center of the widget, there are two plots, each with labels positioned above them. |
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 should limit the line size to about 80 characters for a better view in github.
This is applicable to all the docs in this PR.
No description provided.