Situation
In the current version 0.2.1 the IntelliJ plugin simply uses the whole project for an OFT scan. This is convenient if all occurrences of OFT specification items in documents, code and test are actual part of the intended trace. If however the project contains example files, resources, binaries or other artifacts that can contain specification items that must not be traced, this simple approach fails.
As a user, I expect to be able in the project configuration to choose between either tracing the whole project or selected resources.
If the user wants to select the resources explicitly, OFTs whitelist approach comes into play. OFT can handle a list of files and directories it should scan. Given those, it ignores everything else. Directories are scanned recursively, just like the project directory now is.
To improve the UX, the configuration should have two options to include all source directories known to IntelliJ. That way the user does not have to find and configure them by hand.
An additional multi-line text field should allow adding paths to files or directories relative to the project directory that are also scanned.
The configuration must be integrated into IntelliJ's project configuration.
Acceptance Criteria
- Users can configure to let OFT trace the the whole project
- Alternatively user can configure to trace selected resources
2.1. Users can select if the source directories know to IntelliJ should be included in the trace (on by default)
2.2. Users can select if the test directories know to IntelliJ should be included in the trace (on by default)
2.3. Users can add a list of files or directories to additionally include in the trace (default value doc/)
Situation
In the current version 0.2.1 the IntelliJ plugin simply uses the whole project for an OFT scan. This is convenient if all occurrences of OFT specification items in documents, code and test are actual part of the intended trace. If however the project contains example files, resources, binaries or other artifacts that can contain specification items that must not be traced, this simple approach fails.
As a user, I expect to be able in the project configuration to choose between either tracing the whole project or selected resources.
If the user wants to select the resources explicitly, OFTs whitelist approach comes into play. OFT can handle a list of files and directories it should scan. Given those, it ignores everything else. Directories are scanned recursively, just like the project directory now is.
To improve the UX, the configuration should have two options to include all source directories known to IntelliJ. That way the user does not have to find and configure them by hand.
An additional multi-line text field should allow adding paths to files or directories relative to the project directory that are also scanned.
The configuration must be integrated into IntelliJ's project configuration.
Acceptance Criteria
2.1. Users can select if the source directories know to IntelliJ should be included in the trace (on by default)
2.2. Users can select if the test directories know to IntelliJ should be included in the trace (on by default)
2.3. Users can add a list of files or directories to additionally include in the trace (default value
doc/)