-
-
Notifications
You must be signed in to change notification settings - Fork 270
JUnit Tests
Phil Beauvoir edited this page May 1, 2019
·
8 revisions
Create a new JUnit Plug-in Test Run Configuration and name it "All Tests"
Important settings for each tab (if a setting is not shown below, it is optional):
- Run a single test
- Project:
com.archimatetool.tests
- Test class:
com.archimatetool.tests.AllTests
- Project:
- Test runner: JUnit 4
- Keep JUnit running after a test run when debugging: off
- Run in UI thread: off
- Run an application: [No Application] - Headless Mode
- Launch with: features selected below
com.archimatetool.tests.feature
- Press "Select Required" button to add other required features
- Use features from workspace if available: on (You must select this!!)
- Validate Plug-ins automatically prior to launching: off (Also important!)
- Use default location: on
- Clear the configuration area before launching: on
- Generate a config.ini file as a template: on
If you value and use Archi please consider making a donation. Thanks!
- Developer
- About using Archi or ArchiMate
- Label Expressions
- Add letters to elements to distinguish between layers
- Archi Command Line Interface
- How to create a packaged version of Archi (including configuration and plugins)
- How to create your own report for Archi
- SQL queries in the HTML report
- Pattern based modelling with Archi
- ArchiMate language customization in Archi
- How to disable the "Check for Updates..." menu item
- The Archi.ini File
- Roadmap or potential new features
- Feature requests, the roadmap and managing expectations
- HTML export v3
- List of feature requests and potential roadmap items
- Generate Deliverables (Reporting) Requirements
- Sketch and Canvas revamp ideas
- Ideas for a nice and elegant way to implement profiles and concepts customization
- Roadmap for Archi 2.8
- Known issues
- Other