18 | | '''Requirements:''' Knowledge of testing is not required. The idea candidate should have a firm grasp of the C language with knowledge of C++ as some of the test frameworks will be written using [https://code.google.com/p/googletest/ googletest] and [https://code.google.com/p/googlemock/ googlemock]. Other components of the framework will have to be written from scratch the exact language used for this has not been decided. Learning how to test software is an extremely desirable skill in the software development world any candidate should come in with an eagerness to learn. |
| 18 | '''Possible Test Groups:''' This part is not designed for GSoC, but for future reference |
| 19 | |
| 20 | Creation of 4 separate test groups: |
| 21 | # Host-based (Testing of APIs out-of-hand) |
| 22 | # Operational (Runs on actual hardware or in-simulation), |
| 23 | # RTEMS BSP-specific tests and |
| 24 | # tests specific to a Board. |
| 25 | |
| 26 | '''Requirements:''' Knowledge of testing is not required. The ideal candidate should have a firm grasp of the C language with knowledge of C++ as some of the test frameworks will be written using [https://code.google.com/p/googletest/ googletest] and [https://code.google.com/p/googlemock/ googlemock]. Other components of the framework will have to be written from scratch, the exact language used is will have to be agreed upon by the student and mentor, but should work on both Linux and Windows. |
33 | | = Miscellaneous Sections = |
| 42 | # Modify/use googletest and googlemock to write RTEMS tests, then package them into a separate package like examples-v2== Project Idea 2 == |
| 43 | |
| 44 | # Porting the testsuites into a separate package like examples-v2 would make designing new tests much faster. |
| 45 | # Adding a configuration to only build one of the suites at a time would make designing new tests much faster. |
| 46 | # The ability to port the tests, once developed, back into the test-suite would be beneficial. |
| 47 | = Miscellaneous Sections = |