Changes between Version 382 and Version 383 of Developer/OpenProjects


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

Remove nesting.

Legend:

Unmodified
Added
Removed
Modified
  • Developer/OpenProjects

    v382 v383  
    2626Some of the identified activities which would augment our testing capabilities are listed here:
    2727 *  ''[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].
     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].
    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.
     
    4545
    4646 *  [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.
    50    *  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.
    51    *  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]
     47 * [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.
     48 * '''[wiki:Projects/Open/TesterImprovements]''' - Improve RTEMS Tester (rtems-test) by adding simulator recipes for more simulators. Many more are supported by older sim-scripts.
     49 *  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.
     50 *  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]
    5251 *  General [wiki:TBR/UserManual/RTEMS_Source_Builder RTEMS Source Builder] improvements such as building more host tools, building a GUI, and improving configuration management and creation.
    5352 * Implement recipes in [wiki:TBR/UserManual/RTEMS_Source_Builder RTEMS Source Builder] for all packages in RTEMS [http://git.rtems.org/rtems-addon-packages/ Add on packages], [http://git.rtems.org/rtems-graphics-toolkit/ RTEMS Graphics Toolkit], and packages with just howtos like Lua and LWIP.
     
    6665
    6766 *  ''[wiki:Developer/SMP  Improvements to SMP support]'' - Multiprocessing is of increasing importance. This is a large project and subtasks should be identified before writing any proposal.
    68   *  '''[wiki:Projects/Condition_Variables Condition Variables]''' for the Classic API and supercore.
     67 *  '''[wiki:Projects/Condition_Variables Condition Variables]''' for the Classic API and supercore.
    6968 *  Unified Interrupt and PCI APIs -- [wiki:GSoC/2013/UnifiedAPIs UnifiedAPIs]
    7069 *  '''[wiki:Projects/RumpKernels Rump Kernels]''': provide the hypercall interface for [http://rumpkernel.org/ Rump Kernels] in RTEMS.