Testing

Introduction to Testing
In addition to the integrated JUnit and NUnit testing capabilities, Enterprise Architect enables you to attach arbitrarily complex tests to any model element. Keeping the model elements and the testing documentation in one integrated model significantly improves the communication between the test-team and the software developers and architects. The detailed search facilities make it easy to find failing test cases, test cases not run and tests cases that have been passed. Using the testing and search capabilities, it is easy to navigate through the model and quickly locate problem spots, design flaws and other critical issues. Enterprise Architect is not only a UML Modeling environment, it is also a complete Test Management environment.
Basic Tasks
Simple tasks that you might perform include:
Categories
Typically you create:
- Unit tests for things that are being built, such as Classes and components
- Integration tests to test how components work together
- System tests to ensure the system meets business requirements
- Acceptance tests to test user satisfaction, and
- Scenario tests to test the end-to-end suitability and functionality of the application.
Using Tests
Other tasks that you might perform when working with tests include:
- Import a Scenario as a Test
- Move or Copy Tests Between Test Types
- Import a Test from Other Elements
- Import a Responsibility or Constraint as a Test
- Create a Maintenance Item from a Test
- Generate Test Details Report
- Show Test Script Compartments
- Create Test Documentation.
Note: |
Most of the tasks identified above relate to a tests for a single element. You can make a set of tests available to a number of elements by performing the above tasks on a Test Case element and then associating that Test Case with each of the other elements. The Test Case element also helps to make tests more visible in diagrams, the Project Browser, windows and searches. |