espressif/Unity
1
0
Fork 0
mirror of https://github.com/ThrowTheSwitch/Unity.git synced 2025-10-18 21:02:20 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update UnityGettingStartedGuide.md

Browse Source 
Added more detail on test naming.
This commit is contained in:
Mark VanderVoord
2017-12-06 10:08:56 -05:00
committed by GitHub
parent 62f6cb247a
commit b4aca70fd9
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/UnityGettingStartedGuide.md
View File

@ -100,10 +100,11 @@ find setUp or tearDown when it links, you'll know you need to at least include
an empty function for these. an empty function for these.
The majority of the file will be a series of test functions. Test functions The majority of the file will be a series of test functions. Test functions
follow the convention of starting with the word "test" or "spec". You don't HAVE follow the convention of starting with the word "test_" or "spec_". You don't HAVE
to name them this way, but it makes it clear what functions are tests for other to name them this way, but it makes it clear what functions are tests for other
developers. Test functions take no arguments and return nothing. All test developers. Also, the automated scripts that come with Unity or Ceedling will default
accounting is handled internally in Unity. to looking for test functions to be prefixed this way. Test functions take no arguments
and return nothing. All test accounting is handled internally in Unity.
Finally, at the bottom of your test file, you will write a `main()` function. Finally, at the bottom of your test file, you will write a `main()` function.
This function will call `UNITY_BEGIN()`, then `RUN_TEST` for each test, and This function will call `UNITY_BEGIN()`, then `RUN_TEST` for each test, and