-
Notifications
You must be signed in to change notification settings - Fork 3k
Add Socket test plan #7803
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 Socket test plan #7803
Conversation
@AnotherButler Please review sections from start, to "Running tests". |
@kjbracey-arm please review. |
82fdfe1
to
2f06008
Compare
I'm submitting a test plan for Mbed OS sockets, so that we have reference that describes wanted behaviour, required test environment, and priorities of test cases. This servers as a both documentation and specification. It needs to live with source code, as opposed to Handbook, because it will be extend, modified and fixed for faster cycle than what should be done for Handbook. Part of this document (How to run -section) will be submitted to Handbook with links to this.
2f06008
to
0bb791e
Compare
Adding @ARMmbed/mbed-os-test (as this is a test plan, I believe our first one here? ) |
Copy edit for active voice, inclusion of articles and U.S. spelling.
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.
Looks good
@0xc0170 Why does this need CI? |
Our workflow states PR needs to be green (CI status here as "Required"). We do not currently have subset of tests or what shall be run based on the changes in the PR. We shall discuss this how we can improve this (now that more docs are coming to the repository - test plans, design documents, etc) for 5.11 |
Marking for rc2 for now to make sure we don't lose track of it. |
/morph build |
Build : SUCCESSBuild number : 3036 Triggering tests/morph test |
Test : SUCCESSBuild number : 2809 |
Exporter Build : SUCCESSBuild number : 2652 |
Description
I'm submitting a test plan for Mbed OS sockets, so that we have
reference that describes wanted behaviour, required test environment,
and priorities of test cases.
This serves as a both documentation and specification. It needs to live
with source code, as opposed to Handbook, because it will be extended, modified
and fixed for faster cycle than what should be done for the Handbook.
Part of this document (How to run -section) will be submitted to Handbook
with links to this documentation.
Pull request type