Changes between Version 375 and Version 376 of Developer/OpenProjects


Ignore:
Timestamp:
Feb 12, 2015, 10:12:21 PM (5 years ago)
Author:
Gedare Bloom
Comment:

Start to make the page more consistent-looking.

Legend:

Unmodified
Added
Removed
Modified
  • Developer/OpenProjects

    v375 v376  
    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.
    32  *  Improve the POSIX API Compliance test (testsuites/psxtests/psxhdrs). Details described in https://devel.rtems.org/ticket/2262.
    33  *  Improve [wiki:Projects/GNUToolsTesting  Testing of the GNU Tools] on RTEMS targets
    34  *  Test the [wiki:Projects/POSIXFIFOs  POSIX FIFO Implementation].
     32 *  [wiki:Projects/Open/POSIXCompliance POSIX API Compliance] - Improve the POSIX API Compliance test (testsuites/psxtests/psxhdrs). Details described in Ticket #2262.
     33 *  [wiki:Projects/GNUToolsTesting  Testing of the GNU Tools] - Improve Tools Testing on RTEMS targets
     34 *  [wiki:Projects/POSIXFIFOs  POSIX FIFO tests] - Implement tests for FIFOs.
    3535 *  ''[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.
    3636 *  ''[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.
     
    4444The following areas have been identified for projects related to improving RTEMS development:
    4545
    46  *  Develop a tool for static analysis of stack usage. GCC can produce a ".su" file when used with the -fstack-use option. cflow can be used to produce the control flow to analyze a call stack. The goal of this analysis is for a user to be able to specify a user thread entry point and see the stack usage for each method that thread calls as well as a total usage. This should include application code, RTEMS, and newlib. The scripting will be in Python. cflow will need to be added as an RSB recipe.
    47  *  Improvements in RTEMS Tools for execution and analysis of both functional test results and coverage analysis.
    48    * Complete conversion of coverage reporting to Python and integration into RTEMS Tools. SOCIS 2014 code works but is not production worthy.
    49    * '''RTEMS Tester - rtems-test improvements''' - Add simulator recipes for more simulators. Many more are supported by older sim-scripts.
     46 *  [wiki:Projects/Open/StackAnalysis Static Analysis of Stack Usage] - Develop a tool for static analysis of stack usage. GCC can produce a ".su" file when used with the -fstack-use option. cflow can be used to produce the control flow to analyze a call stack. The goal of this analysis is for a user to be able to specify a user thread entry point and see the stack usage for each method that thread calls as well as a total usage. This should include application code, RTEMS, and newlib. The scripting will be in Python. cflow will need to be added as an RSB recipe.
     47 *  [wiki:Projects/Open/TestingAnalysis] - Improvements in RTEMS Tools for execution and analysis of both functional test results and coverage analysis.
     48   * [wiki:Projects/Open/PythonCoverageReporting] - Complete conversion of coverage reporting to Python and integration into RTEMS Tools. SOCIS 2014 code works but is not production worthy.
     49   * '''[wiki:Projects/Open/TesterImprovements]''' - Improve RTEMS Tester (rtems-test) by adding simulator recipes for more simulators. Many more are supported by older sim-scripts.
    5050   *  Use gcov output as generated by covoar to generate useful reports.  This leverages work by [wiki:GSoC/2011/gcov  support for gcov output] to so tools like gcov and lcov can be used to generate standard coverage reports for RTEMS ([wiki:Projects/GCOVSupport another page here])'' This type of reporting is important for safety certification reviews.
    5151   *  Use gprof output as generated by covoar to generate useful reports.  This is based on the previous project [wiki:GSoC/2011/gprof  Add support for gprof output to covoar]