Changes between Version 23 and Version 24 of Projects/GSoC/TestingReview


Ignore:
Timestamp:
Jul 8, 2012, 9:25:46 AM (7 years ago)
Author:
Xiaochen Pan
Comment:

/* Comparison Note */

Legend:

Unmodified
Added
Removed
Modified
  • Projects/GSoC/TestingReview

    v23 v24  
    309309= Comparison Note =
    310310
     311== Selection Criteria ==
     312
    311313
    312314The list is listed in selection priority order. In other words, CMock is considered to be the top competitive choice for this project. The priority is calculated basing on the following criteria:
     
    322324
    323325 * The frist few criteria have the higher screening weight. The following ones are also very important. The xUnit architecture support is equivalently important in the sense that frameworks supporting xUnit architecture have edges on better handling relationship between test cases than frameworks that doesn't support.
    324 
    325 The RTEMS based tests are carried out with '''BSP=sis''' and '''CPU=sparc'''. For other CPUs and BSPs, further RTEMS based testing of converted current test suites would be simulated in future with the selected frameworks.
    326 
    327 '''Google Test and CxxUnit''' are testing frameworks with programming language C++, with the large set of self-produced libs and comprehensive testing functionalities, they are considered being too big to run for RTEMS based testing, with some cpus and bsps for RTEMS having only limited memory.
    328 
    329 Although '''mocking capability''' are compared between the frameworks, no mocking functions are constructed in the RTEMS-based test simulations temporarily.
    330 
    331 Even though all ten frameworks are compared in the above listed aspects, '''major simulation effort''' is concentrated on the top five. There is no need to simulate all of them if the test results for any top five framework is satisfiable.
    332 
    333 For '''host-based testing framework evaluation''', because host based tests are tests that does not rely on rtems APIs, I build and run the tests which are written in each framework with the purpose of test the framework itself. The screenshot are showed in each framework subpage. The screenshot is displayed only to compare the readability of the test output and amount of information contained in each framework.
     326== Simulation Environment ==
     327
     328
     329The RTEMS based tests are carried out with BSP=sis and CPU=sparc. For other CPUs and BSPs, further RTEMS based testing of converted current test suites would be simulated in future with the selected frameworks.
     330== C++ Frameworks ==
     331
     332
     333Google Test and CxxUnit are testing frameworks with programming language C++, with the large set of self-produced libs and comprehensive testing functionalities, they are considered being too big to run for RTEMS based testing, with some cpus and bsps for RTEMS having only limited memory.
     334== Mock ==
     335
     336
     337Although mocking capability are compared between the frameworks, no mocking functions are constructed in the RTEMS-based test simulations temporarily.
     338== Simulation Effort ==
     339
     340
     341Even though all ten frameworks are compared in the above listed aspects, major simulation effort is concentrated on the top five. There is no need to simulate all of them if the test results for any top five framework is satisfiable.
     342== Host-based Testing ==
     343
     344
     345For host-based testing framework evaluation, because host based tests are tests that does not rely on rtems APIs, I build and run the tests which are written in each framework with the purpose of test the framework itself. The screenshot are showed in each framework subpage. The screenshot is displayed only to compare the readability of the test output and amount of information contained in each framework.