apps/testing: Add a cmocka framework for network testing

[zs39]

Summary

Provides a network automated testing framework, including the main directory structure and Makefile, CMakeLists, Kconfig and other files such as tcp.

Impact

N/A

Testing

Local qemu environment verification

[nuttxpr]

[Experimental Bot, please feedback here]

No, this PR summary does not adequately meet the NuttX requirements. While it provides a basic outline, it lacks crucial detail. Here's why:

• Summary: "Provides a network automated testing framework" is too vague. What kind of network tests? TCP only, as mentioned later? What aspects of networking are being tested? The mention of tcp.c implies a specific test, not a framework. This section needs to explain the purpose and scope of the framework. It should also clarify the relation between the framework and the seemingly specific tcp.c file. Furthermore, the relationship to existing testing infrastructure (if any) should be discussed.

• Impact: Claiming "N/A" (Not Applicable) for all impact categories is highly unlikely for a new testing framework. Consider the following:

  • New Feature: This is clearly a new feature and should be stated as such.
  • Impact on User: Does this impact how users run existing tests? Will they need to learn a new testing interface?
  • Impact on Build: Adding a new framework undoubtedly changes the build process, even minimally. At least the build target for the test framework itself needs description. Specify any new build options or dependencies.
  • Impact on Hardware: While the framework itself might not directly impact hardware, its usage might. Does it require specific hardware configurations or features?
  • Impact on Documentation: A new feature requires documentation. This PR should either include documentation updates or explicitly state why they are not yet included (with a plan for adding them).
  • Impact on Security/Compatibility: While these might genuinely be N/A, it's better to explicitly state that these aspects have been considered and no impact is expected, rather than just using a blanket "N/A".

• Testing: "Local qemu environment verification" is insufficient. What specific tests were run? What were the expected outcomes? The provided log sections are empty. Include actual log output demonstrating the tests and their results. Specify the QEMU configuration (e.g., the machine type). If only tcp.c is being tested, that should be explicitly stated. The build host details are also missing, violating the requirement.

In short, the PR description needs significant expansion to meet the NuttX requirements. More details are needed in every section to make it a complete and informative description of the changes.

[cederom]

Thank you @zs39 :-)

• This is just the initial template with no tests that you will add soon right?
• Please let us know how this testing work at current stage, can you provide a test log?
• Please note that testing is currently being reorganized and will probably change directory structure soon The placement of cases under testing is a bit messy, and cases of the same type need to be merged #2931. There are some tests already planned in net/cmocka please make sure you are not duplicating the work?

[xiaoxiang781216]

Thank you @zs39 :-)

• This is just the initial template with no tests that you will add soon right?

Yes.

• Please let us know how this testing work at current stage, can you provide a test log?

will provide in the next patchset.

• Please note that testing is currently being reorganized and will probably change directory structure soon The placement of cases under testing is a bit messy, and cases of the same type need to be merged #2931. There are some tests already planned in net/cmocka please make sure you are not duplicating the work?

yes, that's why we want upstreaming nettest first to avoid the conflct with the structure layout.