Quick Search
Dashboard
KM: Agile Software Development
…
Agile Software Development Home
Advanced testing
JigZaw
JigZaw Design Principles and Drivers
Main components
Agile and Software Architecture
Agile Mindset and Methodology
Strategies
Tactics
Popular Pieces
JigZaw
Enterprise Maven Infrastructure
Installation and Deployment Automation
Maven FAQ
Test Frameworks and Tools
Lightweight alternatives to heavyweight technologies
Resources
Presentation repository
Glossary
Page Operations
V
iew
A
ttachments (0)
Info
Watchers
Favourites
Browse Space
Pages
Blog
Labels
Attachments
Bookmarks
Mail
Forums
Advanced
Activity
View a printable version of the current page.
Log In
Sign Up
KM: Agile Software Development
JigZaw Design Principles and Drivers
Added by
Erik Drolshammer
, last edited by
Erik Drolshammer
on Mar 20, 2009 (
view change
)
Labels:
Enter labels to add to this page:
Looking for a label? Just start typing.
Divide and conquer
Single-responsibility principle
Group tests according to their prerequisites
Always choose the the cheapest and simplest solution which solves the problem
JigZaw principles applied to test maintenance
See also
Mapping between requirements and tests
Child Pages (5)
Hide Child Pages
|
View in Hierarchy
Always choose the the cheapest and simplest solution which solves the problem
Divide and conquer
Group tests according to their prerequisites
JigZaw Design Principles and Drivers - OLD
Single-responsibility principle
All content on this wiki is licensed under a
Creative Commons Attribution 3.0 Unported License
.
Page Operations
Browse Space