SDA SE Wiki

Software Engineering for Smart Data Analytics & Smart Data Analytics for Software Engineering

User Tools

Site Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
research:cultivate:history [2010/11/07 07:07]
127.0.0.1 external edit
research:cultivate:history [2018/05/09 01:59] (current)
Line 1: Line 1:
 +===== Rationale =====
 +
 +<​note>​This page contains some of the rationale that led to the decision about a new test framework in the Agile Lab 2009a. The main results have been: It should be easy to write test data just like any other Java code, Testers prefer to use JUnit as a Frontend (over FitNesse), Factbases should be pregenerated so that the test execution is fast.</​note>​
 +
 +==== What do we wan't? ====
 +
 +  * Stuff to test:
 +    - Java parts
 +    - Prolog parts
 +
 +  * General Criterias
 +    - Independence of tests and code
 +
 +  * Evaluation Criterias for Prolog tests:
 +    - Fast Tests
 +    - Automated Tests
 +    - Real classes as testdata
 +    - Clear relations between testdata, tests and code
 +    - Test cases should be easy to write
 +    - Test framework should be easy to use
 +
 +==== What do we have? ====
 +
 +  - Java Parts 8-)
 +    * Plain Tests: Test of java cultivate core functionality
 +    * Plugin Tests: Test of cultivate functionality related to eclipse
 +
 +  - Prolog Parts :-\
 +    * Prolog Tests (based on plugin tests):
 +      - Slow :-(
 +      - No automation because of a bug :-(
 +        * plwin does not close if test fails
 +      - Testdata are no real classes :-(
 +      - Testdata in the tests 8-)
 +      - Assertions not intuitive to check :-(
 +      - Easy to use, since junit test integration is good in eclipse 8-)
 +      - JTransformer predicates readily available for the tests. 8-)
 +      - Same internal mechanisms as in Cultivate itself. :-) 
 +    * Fitnesse Tests
 +      - Fast 8-)
 +      - Automation works 8-)
 +      - Real classes as test data 8-)
 +      - Traceability between testdata and factbases not given :-(
 +      - Easy writable tests through wiki syntax 8-)
 +      - Fitnesse is unintuitive for tests at the beginning :-(
 +      - JTransformer predicates need to be explicitly consulted. :-(
 +    * JTransformer (based on plugin-tests)
 +      - Slow :-\
 +      - Automation works 8-)
 +      - Testdata are real classes, but zipped :-\
 +      - Testdata in the tests 8-)
 +      - Assertions not intuitive to check :-(
 +      - Easy to use, since junit test integration is good in eclipse 8-)
 +
 +
 +==== What can we do? ====
 +
 +  * Assumptions:​
 +    * One project for the test framework (cultivate.tests)
 +    * One test project per project to test (e.g. cultivate.core => cultivate.core.tests)
 +
 +  * Fitnesse
 +    * One sourcefolder per factbase in each test project and precompile and filter factbases based on sourceFolderT 8-)
 +    * Prepare Fixture that consults all JTransformer predicates.
 +
 +  * Junit Tests
 +    - One sourcefolder per factbase in each test project
 +      * Still needs slow plugin tests :-/
 +    - additionaly precompile and filter factbases based on sourceFolderT
 +      * would get rid of plugin tests and move to plain prolog tests 8-)
 +    - Improve assertion checking for prolog results 8-)
 +    - Timeout for prolog tests, so that plwins get removed.
 +
 +  * Write a test environment for plain prolog tests
 +    * Java Prolog Queries not testable :-(
 +    * Relation between factbase and source code not visible again :-(
  
research/cultivate/history.txt · Last modified: 2018/05/09 01:59 (external edit)

SEWiki, © 2019