Changes between Version 391 and Version 392 of Developer/OpenProjects


Ignore:
Timestamp:
Feb 14, 2015, 7:29:22 PM (4 years ago)
Author:
Gedare Bloom
Comment:

Relocate some more project pages.

Legend:

Unmodified
Added
Removed
Modified
  • Developer/OpenProjects

    v391 v392  
    2525
    2626Some of the identified activities which would augment our testing capabilities are listed here:
    27  *  ''[wiki:Projects/TestingImprovements RTEMS Testing]. Testing for RTEMS, including Unit, Regression operational and building a custom test harness.  No prior knowledge of software testing is required. (SOCIS)''
    28  *  [wiki:Developer/Testing/Specifications RTEMS Test Specification] - Need a formal test specification.  Ideally, inspired by http://softwaretestingstandard.org/ some notes about existing test specifications can be found http://www.rtems.org/wiki/index.php/GoogleCodeInProjects#Test_Documentation_Files_update .
    29  *  [wiki:RTEMS_Test_Screen_Validation RTEMS Test Screen Validation] - This requires expertise in a unit testing framework, probably DejaGnu, and will probably need to be tied into [http://git.rtems.org/rtems-testing/ rtems-testing] and [http://git.rtems.org/rtems-tools/ rtems-tools].
     27 *  ''[wiki:Projects/Open/TestingImprovements RTEMS Testing]. Testing for RTEMS, including Unit, Regression operational and building a custom test harness.  No prior knowledge of software testing is required. (SOCIS)''
     28 *  [wiki:Projects/Open/TestSpecification RTEMS Test Specification] - Need a formal test specification.  Ideally, inspired by http://softwaretestingstandard.org/ some notes about existing test specifications can be found http://www.rtems.org/wiki/index.php/GoogleCodeInProjects#Test_Documentation_Files_update .
     29 *  [wiki:Projects/Open/TestScreenValidation RTEMS Test Screen Validation] - This requires expertise in a unit testing framework, probably DejaGnu, and will probably need to be tied into [http://git.rtems.org/rtems-testing/ rtems-testing] and [http://git.rtems.org/rtems-tools/ rtems-tools].
    3030 *  '''[wiki:TBR/UserManual/RTEMS_Coverage_Analysis  Test Coverage Analysis]''' - In general, there are specific areas that need actual tests written and areas in which the RTEMS Project tools need work to improve our testing ability. Look until Tools and Development Environment for those projects. This section focuses on improvements to coverage by adding more test cases, reworking code to eliminate the need for additional test cases, etc.. Eliminating dead code and reaching 100% coverage helps reduce the likelihood of new and recurrent bugs.
    3131 *  [wiki:Projects/Open/SimulatorUpdates Simulator Updates] - Test BSPs that target simulators to find and fix problems. It is important to ensure that BSPs which run on simulators pass all tests possible.
    3232 *  [wiki:Projects/GNUToolsTesting  Testing of the GNU Tools] - Improve Tools Testing on RTEMS targets
    3333 *  [wiki:Projects/POSIXFIFOs  POSIX FIFO tests] - Implement tests for FIFOs.
    34  *  ''[wiki:TBR/Delete/POSIXTimingTests  POSIX Timing Tests]'' - Many have been implemented but there should be more cases worth timing. Precise status is stored in a .csv file in the psxtmtests directory in the source tree.
    3534 *  ''[wiki:Projects/POSIXComplianceTestSuite  POSIX Compliance Test Suite]'' There are multiple aspects to this project. One aspect is the addition of interface compliance tests for rest of POSIX API. Another part is running third party C Library and POSIX API tests (e.g. from glibc, *BSD, or the older Intel POSIX suite)  against RTEMS and newlib. Ultimately, we would like functional coverage test results on newlib as well as RTEMS. Results of third party existing tests would have to be carefully evaluated to ensure appropriateness and results. Related: Improve the POSIX API Compliance test (testsuites/psxtests/psxhdrs). Details described in Ticket #2262.
    3635 *  [wiki:GSoC/Projects/TestTemplate RTEMS Test Template] - Improve by adding functionality