Changes between Version 337 and Version 338 of Developer/OpenProjects


Ignore:
Timestamp:
Jun 20, 2013, 9:17:49 PM (6 years ago)
Author:
C Rempel
Comment:

/* Testing */

Legend:

Unmodified
Added
Removed
Modified
  • Developer/OpenProjects

    v337 v338  
    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.
    28  *  '''[wiki:RTEMS_Test_Coverage  Test Coverage Analysis]''' - Improve coverage by adding more test cases. Eliminating dead code and reaching 100% coverage helps reduce the likelihood of new and recurrent bugs.
     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:RTEMS_Test_Coverage  Test Coverage Analysis]''' - Improve coverage by adding more test cases. Eliminating dead code and reaching 100% coverage helps reduce the likelihood of new and recurrent bugs. (SOCIS)
    2929  *  Write a tutorial, modify a [http://en.wikipedia.org/wiki/Fault_injection#Research_tools fault injection tool] to work with RTEMS
    3030 *  Test the [wiki:Projects/POSIXFIFOs  POSIX FIFO Implementation].
     
    3232 *  Improve [wiki:Projects/GNUToolsTesting  Testing of the GNU Tools] on RTEMS targets
    3333 *  ''[wiki:TBR/Delete/POSIXTimingTests  POSIX Timing Tests]''
    34  *  ''Add [wiki:RTEMSgcov_  support for gcov output] to covoar so tools like gcov and lcov can be used with RTEMS ([wiki:Projects/GCOVSupport another page here])''
     34 *  ''Add [wiki:RTEMSgcov_  support for gcov output] to covoar so tools like gcov and lcov can be used with RTEMS ([wiki:Projects/GCOVSupport another page here])'' (SOCIS)
    3535 *  ''[wiki:Projects/POSIXComplianceTestSuite  POSIX Compliance Test Suite]''
    36  *  [wiki:Projects/Open/SimulatorUpdates Simulator Updates] - This is a new idea for a project and has not been described beyond what is here. Ask on the rtems-devel mailing list for more advice. The RTEMS Project relies heavily on multiple FOSS simulators including qemu and skyeye. We have multiple BSPs which are tested on simulators. Each BSP will need to be tested against the current release and development version of each simulator. If there is a problem, then the issue will have to be identified (possibly using something like git bisect) and the student will have to fix it in the simulator. As an example of this, we believe some ARM BSPs which worked on older versions of Skyeye no longer work on the current version. In some cases, the RTEMS Project is carrying unmerged patches for a simulator (at least qemu m68k and arm) which need to be updated to their development head and submitted. You will try to get the simulator developers to include RTEMS hello world and ticker executables for BSPs their simulator supports in their simulator tests to avoid future breakage. And you will ensure that the scripts in rtems-testing/sim-scripts are working for the latest version of the simulator. We would also like instructions on running the leon BSPs on qemu. Please ask questions. This is a broad project.
     36 *  [wiki:Projects/Open/SimulatorUpdates Simulator Updates] - This is a new idea for a project and has not been described beyond what is here. Ask on the rtems-devel mailing list for more advice. The RTEMS Project relies heavily on multiple FOSS simulators including qemu and skyeye. We have multiple BSPs which are tested on simulators. Each BSP will need to be tested against the current release and development version of each simulator. If there is a problem, then the issue will have to be identified (possibly using something like git bisect) and the student will have to fix it in the simulator. As an example of this, we believe some ARM BSPs which worked on older versions of Skyeye no longer work on the current version. In some cases, the RTEMS Project is carrying unmerged patches for a simulator (at least qemu m68k and arm) which need to be updated to their development head and submitted. You will try to get the simulator developers to include RTEMS hello world and ticker executables for BSPs their simulator supports in their simulator tests to avoid future breakage. And you will ensure that the scripts in rtems-testing/sim-scripts are working for the latest version of the simulator. We would also like instructions on running the leon BSPs on qemu. Please ask questions. This is a broad project. (SOCIS)
    3737 * [wiki:GSoC/Projects/TestTemplate RTEMS Test Template] - Improve by adding functionality
    3838 * [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 .