Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

Changes between Version 1 and Version 2 of Developer/Projects/Open/TestTemplate


Ignore:
Timestamp:
12/11/14 02:21:10 (10 years ago)
Author:
Chris Johns
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Projects/Open/TestTemplate

    v1 v2  
    2020did as of the time of the bug-report.
    2121
    22 # Create a new directory for the test. '''Note:''' handled by http://git.rtems.org/rtems-testing/tree/rtems-test-template
    23 # Create a new Makefile.am.  This normally involves a lot of copy and paste from an existing test. '''Note:''' handled by http://git.rtems.org/rtems-testing/tree/rtems-test-template
    24 # Add a new init.c file.  Which may be enough for simple tests. '''Note:''' handled by http://git.rtems.org/rtems-testing/tree/rtems-test-template
    25 # Add a test.doc file for the documentation. '''Note:''' handled by http://git.rtems.org/rtems-testing/tree/rtems-test-template
    26 # Add a test.scn file with the output of the test. '''TODO:''' probably could add a make-scn to rtems/make/leaf.cfg or rtems/c/src/make/leaf.cfg through a clever call to a simulator and a log file
    27 # Modify the top level Makefile.am. '''TODO:''' probably could add this functionality to rtems/bootstrap
    28 # Modify the top level configure.ac. '''TODO:''' probably could add this functionality to rtems/bootstrap
    29 # Run bootstrap. '''TODO:''' make this an option when running the script in http://git.rtems.org/rtems-testing/tree/rtems-test-template
    30 # Add a copy and paste .cvsignore. '''Note:''' outdated, possibly .gitignore
    31 # Write a ChangeLog with several entries. '''Note:''' replaced ChangeLog with git functionality
     221. Create a new directory for the test. '''Note:''' handled by http://git.rtems.org/rtems-testing/tree/rtems-test-template
     231. Create a new Makefile.am.  This normally involves a lot of copy and paste from an existing test. '''Note:''' handled by http://git.rtems.org/rtems-testing/tree/rtems-test-template
     241. Add a new init.c file.  Which may be enough for simple tests. '''Note:''' handled by http://git.rtems.org/rtems-testing/tree/rtems-test-template
     251. Add a test.doc file for the documentation. '''Note:''' handled by http://git.rtems.org/rtems-testing/tree/rtems-test-template
     261. Add a test.scn file with the output of the test. '''TODO:''' probably could add a make-scn to rtems/make/leaf.cfg or rtems/c/src/make/leaf.cfg through a clever call to a simulator and a log file
     271. Modify the top level Makefile.am. '''TODO:''' probably could add this functionality to rtems/bootstrap
     281. Modify the top level configure.ac. '''TODO:''' probably could add this functionality to rtems/bootstrap
     291. Run bootstrap. '''TODO:''' make this an option when running the script in http://git.rtems.org/rtems-testing/tree/rtems-test-template
     301. Add a copy and paste .cvsignore. '''Note:''' outdated, possibly .gitignore
     311. Write a !ChangeLog with several entries. '''Note:''' replaced !ChangeLog with git functionality
    3232
    3333Refine this initial statement to include: project deliverables (code, docs, testing), required/suggested methodology, standards of quality, possible goal extensions beyond the main objective.
     
    3636
    3737'''Possible Goal Extensions:'''
    38 # Make the unit tests more in compliance with http://softwaretestingstandard.org/ by filling in the .doc with the needed information
    39 # Align the tests with the POSIX and RTEID standards through the use of doxgen comments
     381. Make the unit tests more in compliance with http://softwaretestingstandard.org/ by filling in the .doc with the needed information
     391. Align the tests with the POSIX and RTEID standards through the use of doxgen comments
    4040
    4141'''Requirements:''' List the requirements and level of expertise you estimate are required by the developer tackling this project will have to have: Required level of programming language(s), specific areas of RTEMS or tools, level of familiarity with RTEMS, cross-development, GNU/Linux, etx., development/documentation/testing tools, mathematical/algorithmic background, other desirable skills.