SourceForge.netOrientation in Objects GmbH
About
Overview
Goals
J2EE and Test
Why frameworks
Tooling philosophy
Future
SourceForge Status
Our SourceForge Site


Products
Recorder
Player
Oracle
Workbench
Ideas


Use
Install
Support for users
Javadocs


Contribute
Work with us
Contact us
) About - Why Frameworks )
< Multitier Application Scenario - Web Application Frameworks >

Bugkilla and J2EE Web Application Test

Build in Tests

Build in Tests (BIT) are a kind of software testing that tries to lower quality assurance costs by considering testability in the design of applications. A testing-aware design should provide:

  • A clear mapping between domain objects and J2EE-components
  • An easy translation of domain state to status mechanisms in J2EE
  • The ability to monitor and query relevant status of components

This can be achieved at component design level as well as at framework design level. The J2EE blue prints strongly recommend the use of frameworks to reduce development and maintainance costs. The BIT concept forces the following ideas.

  • Determine the possible support of existing web application frameworks for BIT
  • The development of a framework with special BIT-features
  • The detection of rules and guidelines for BIT at component development level

Bugkilla focusses on existing frameworks like Sun WAF or Apache Struts. We do not plan to invent another framework. Instead we spend a little energy on some guidelines for an Build In Tests enabled test process.

Rule 4

Determine the possible support of existing web application frameworks for Build in Tests.

Rule 5

Check if you are following a Build In Tests enabling development process. If not change your process.

< Multitier Application Scenario - Web Application Frameworks >