• View
• Edit
• History
• Print

Tests

Principle

What test would Seedea pass for you to consider it to be a success or... a version 1.0 let's say?

Final user "use cases"

• "typical" situation, a scenario without problems about the average user needs.
  • derivatives of this situations
• worst case scenari

Checklist

1. "strategically" (based on the web evolution) having a well defined API and facilitate interactions with those format could be a good move, does it allow that?

Tools

• Integrate Seedea.Testing, especially the target systems and the method

Inspirations

• Test driven development

To add

• link with the marketing/communication page
• drawings from the 16/09/2008