Changes between Version 34 and Version 35 of DeveloperGuidelinesTesting
- Timestamp:
- 01/11/09 21:03:16 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DeveloperGuidelinesTesting
v34 v35 47 47 == Boundary Testing (should do) == 48 48 Checks functionality of modules against [BluePrints specs]: Building the Right Code 49 * Could use something like [http://fitnesse.org/FitNesse.AcceptanceTests Fitnesse] or [http://rspec.info/ Rspec] to provide testable specs50 49 51 50 This sees the application as a black box & so the same tests could be run here against both the Python & PHP versions, for instance. … … 55 54 * [http://jakarta.apache.org/jmeter/ JMeter] 56 55 This is done by the Testers who accept the Code as a result. 56 57 Could use something like [http://fitnesse.org/FitNesse.AcceptanceTests Fitnesse] or [http://rspec.info/ Rspec] to provide testable specs 57 58 58 59 == Integration Testing (good thing) ==