Search results
Create the page "Branch Test Coverage" on this wiki!
Page title matches
- Branch Test Coverage Participants examine branch test coverage to discover potential errors in their code.4 KB (564 words) - 13:33, 8 September 2018
-
76 B (9 words) - 17:46, 8 March 2017
Page text matches
- :* ''Tests'': Run a code coverage tool to identify untested code. Write a test that covers it. ...ersion 3.8.x of the product evince (a document viewer), the current stable branch is 3.20, so may not be current.20 KB (3,138 words) - 01:29, 7 February 2017
- Branch Test Coverage Participants examine branch test coverage to discover potential errors in their code.4 KB (564 words) - 13:33, 8 September 2018
- Testing and Coverage Assignment Participants write unit tests (in [[:Category:Google Test|Google Test]]) to identify bugs in a C++ class5 KB (756 words) - 13:36, 8 September 2018
- Regression Test Assignment Participants write unit tests (in [[:Category:Google Test|Google Test]]) to establish reliable regression tests for a C++ class6 KB (847 words) - 13:37, 8 September 2018
- ...t.org/ jUnit] testing framework and [http://www.eclemma.org/jacoco/ JaCoCo coverage tool] instead of GoogleTest and gcov. # Setting up testing framework and how to write a unit test; [[Unit Test With GoogleTest Activity]]5 KB (661 words) - 17:09, 27 February 2017
- * Test User Installation Instructions * Group 2: Code Base Understanding - Examine Branch Test Coverage (Activity) -- Josh & Helen5 KB (683 words) - 21:05, 19 October 2017
- * Complete the [[:Category:Test_User_Installation_Instructions_(Pathway)|Test User Installation Instructions]] pathway. : - Possibly: Test cases for feature are complete.0 members (0 subcategories, 0 files) - 11:21, 6 August 2020
- ...e contribution is''': unit tests accepted into the project's codebase, and test results logged on issue tracker or otherwise accepted by the community. *Examine test plan/documentation, if it exists.0 members (0 subcategories, 0 files) - 00:34, 9 March 2017