未验证 提交 741e02f2 编写于 作者: O openharmony_ci 提交者: Gitee

!1200 Done! 895 update contribution guide

Merge pull request !1200 from wusongqing/TR895
......@@ -26,4 +26,4 @@ OpenHarmony 2.0 Canary. [Learn more](en/release-notes/openharmony-2-0-canary.md)
OpenHarmony_v1.x_release: OpenHarmony v1.1.2 LTS. [Learn more](en/release-notes/OpenHarmony-v1.1.2-LTS.md)
[More versions](https://gitee.com/openharmony/docs/blob/master/en/release-notes/)
[More versions](en/release-notes/)
......@@ -344,7 +344,7 @@ The following table describes the subsystems of OpenHarmony. For details about t
## Getting Started<a name="section44681652104210"></a>
For details, see [https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/Readme-EN.md](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/Readme-EN.md).
For details, see [device-dev/quick-start/Readme-EN.md](device-dev/quick-start/Readme-EN.md).
## Code Repository Addresses<a name="section107651249181914"></a>
......@@ -364,7 +364,7 @@ OpenHarmony archived projects: [https://gitee.com/openharmony-retired](https://
## Source Code Downloading<a name="section39011923144212"></a>
For details about how to obtain the source code of OpenHarmony, see [Source Code Acquisition](https://gitee.com/openharmony/docs/blob/master/en/device-dev/get-code/source-code-acquisition.md).
For details about how to obtain the source code of OpenHarmony, see [Source Code Acquisition](https://gitee.com/openharmony/docs/blob/master/en/device-dev/get-code/sourcecode-acquire.md).
## How to Participate<a name="section19611528174215"></a>
......
......@@ -4,6 +4,7 @@
- [Code of Conduct](code-of-conduct.md)
- [Code Contribution](code-contribution.md)
- [Contribution Process](contribution-process.md)
- [Auto-Test](../readme/test_subsystem.md)
- [Documentation Contribution](documentation-contribution.md)
- [Writing Instructions](writing-instructions.md)
- [Communication in Community](communication-in-community.md)
......
......@@ -22,6 +22,10 @@ For details about how to participate in Special Interest Group (SIG), see **SIG
For details about how to contribute to code, see [Code Contributing ](code-contribution.md).
## Auto-Test
For details about how to develop test cases based on test requirements, see [Test Subsystem](../readme/test_subsystem.md).
## Contributing Documents<a name="en-us_topic_0000001053868136_section11234185012131"></a>
For details, see [Documentation Contribution](documentation-contribution.md).
......
......@@ -63,7 +63,7 @@ subsystem # Subsystem
### Writing Test Cases
This test framework supports test cases written in multiple programming languages and provides different templates for different languages.
**C++ Test Case Example**
#### C++ Test Case Example
- Naming rules for source files
......@@ -243,7 +243,7 @@ Example:
|Fuzz test |FUZZ|
**JavaScript Test Case Example**
#### JavaScript Test Case Example
- Naming rules for source files
......@@ -731,7 +731,7 @@ When the build is complete, the test cases are automatically saved in the **out/
1. On Windows, create the **Test** directory in the test framework and then create the **testcase** directory in the **Test** directory.
2. Copy **developertest** and **xdevice** from the Linux environment to the **Test** directory on Windows, and copy the test cases to the **testcase** directory.
>**Note**: Port the test framework and test cases from the Linux environment to the Windows environment for subsequent execution.
>**Note**: Port the test framework and test cases from the Linux environment to the Windows environment for subsequent execution.
3. Modify the **user_config.xml** file.
```
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册