JarCastingsubsteps-framework 
Welcome to the substeps-framework project!
The new home for:
| Project | api docs |
|---|---|
 |
 |
 |
 |
 |
n/a |
 |
n/a |
 |
n/a |
Requirements
- Java 11+
- Scala 2.12.10 (included)
1.1.7
- Removed the direct dependency on the tools.jar for the custom doclet, replaced with new Custom doclet and javadoc tools
- Java 11 compatibility
- Improved the forked process shutdown
1.1.5
- Fix a bug with the Glossary builder not setting section correctly.
1.1.4
- Fix for #77 Glossary Builder mojo unable to load step implementation meta information from jars
1.1.3
- Changed the root report page to be index.html. Added a redirect page in for the old.
- Glossary changes - got rid of the noise when extracting substeps tag info. Enabled the migration to new qualified custom glossary tags 'org.substeps.step.example' and 'org.substeps.step.section'
- some sonar suggested fixes
- If a -Denvironment= variable is set, pass through to the forked VM process. Can be overriden from the parent process using the vmArgs parameter in config if required.
- Multiple execution configs cause issues with the report when running in forked mode, only the second set of results are visible. #74
- Added scalastyle config
1.1.2
- Initialisation classes added through config were being ignored. #67
- Updated the annotated conf example
- bug in the glossary builder, not excluded classnames in the config resulted in a null pointer. #66
- failure in scenario setup methods results in missing results data and report building failure. #65
- added config to the pom to run scala tests in all projects
- guava upgrade
1.1.1
- Prevent duplicate step implementations being created in the glossary json file. Fixes #62
1.1.0
- Moved substeps config to a single org.substeps hierarchy, existing overrides will still be used, but config should be updated
- Moved maven pom configuration to config files (multiple). Maven plugin will print out the new config from existing pom settings, see [1.1.0 Upgrade notes](1.1.0 Upgrade.md) for further details
- Added an exclusion filter to the config for the glossary builder under
org.substeps.config.glossary.excludeStepImplementationClassNames - Scenario and Outline results files appended with their offset to enable outlines that don't include a dynamic name parameter or duplicate named scenarios. Issue #49 and #53
- Added an annotated config file for reference
1.0.6
- Redacted some of the output of the config
- Passed the name of the running feature and scenario into the context.
- RemoteWebDriverFactory sets up additional information to pass though via capabilities (current git branch, version)
- Made the report builder more robust when there are no tests run
- Modified the Substeps exceptions to limit the stack trace
- Improved error message when no tests are run
- escaped < and > in the glossary data
- Corrected the path to the screenshot images to be relative so that they work when served off a server and locally.
- various sonar fixes
- Upgraded guava to 21.0 - required to support selenium 3.3 and latest firefox drivers
1.0.5
- Single Maven plugin, glossary functionality moved into the same plugin that provides execution and report building, original glossary-builder kept in place to avoid breakages. Removed XML variant of the Glossary in favour of json.
1.0.4
- Added a checkbox to the report to optionally hide skipped steps
- Substeps Mojos - Failures should prevent the Maven install phase from running; The runner mojo will throw a MojoFailureException only if the verify phase is not planned. The Report Builder will throw any such exception if one is encountered in the maven session.
- Report enhancements
- Upgraded Bootstrap to 3.3.7
- 3 progress bars rather than one, toggle to show data in original tabular form
- Step implementation method usage report (Beta)
- Replaced hand rolled recursive File listing with commons.io implementation
- Fixed Issue #24 - ExecutionResultsCollector didn't work with forked mode
- Added 3rd colour to usage report pie charts to show not run state
- Corrected the path to the screenshots in the report data and the final report
- Replaced Apache config with Typesafe Config - similar functionality but provides better nesting of properties, variable substitution
- Added System property switch to use original properties files over new .conf files (
-Dsubsteps.use.dot.properties=true) - Enable any parameters to be substituted with values from config - user ${config.expression}. Delimitters can be specified and Charset conversion too, see core-api reference.conf for details
- Enabled arguments to be evaluated at runtime against objects in the execution context
1.0.3
- Added capability for outline descriptions to contain parameter placeholders that can be populated from the example tables, each iteration of the outline potentially then being named something different.
- Default core config
- Uncalled and Unused step impls written to json file rather than logs, overridable via a config property
- Added scala into the mix
- Execution now generates number of data files, report now generated from those files.
- Split up the Maven runner into two, one to run, the other to build the report in the verify phase
- Maven runner mojo doesn't throw a build failed exception, just adds as a result - allows the report to be built and subsequent tear down phases to run
1.0.0
- Forked from G2G3.Digital as no longer being maintained. Group renamed to org.substeps and version number reset to 1.0
com.technophobia.substeps releases
2.0.0
- New single repo to make ongoing maintenance / build dependencies easier
- Enabled a scenario name to be used in addition to a feature file to restrict what gets run
- Travis-CI now produces publicly accessible snapshot builds
- Java 8 requirement, we haven't included any Java 8 features ourselves yet, but the latest libraries we use do
