Releases: veepee-oss/gingerspec
Releases · veepee-oss/gingerspec
2.2.17
2.2.16
2.2.15
2.2.14
2.2.13
- Created a new formatter capable of transforming the feature files into a html document. This is for auto-generating the documentation that will be published in GitHub pages (https://veepee-oss.github.io/gingerspec/index.html)
- Some unnecessary features and runner classes were removed, general code-cleanup
- Completely rewrite the Selenium, Rest and SQL features, so they can be displayed with nice sections in the final html page. The Selenium feature was rewritten using examples from https://testpages.herokuapp.com/
- Many Selenium steps were rewritten to avoid using a previous step for storing webelements
- Test page used during the pipeline execution for testing the selenium steps was removed and is no longer using demoqa.com, but a static page from https://testpages.herokuapp.com/
- Improved debug messages for selenium steps
- @rest annotation was removed. Rest steps will now automatically bootstrap a new instance of rest-assured client if it doesn't exists
- @Sql annotation was removed. Now GingerSpec will automatically close any open database connection at the end of the scenario
Contributors
rest and Sql
Assets 2
2.2.12
- Updated step so Rest client from rest assured is not initialized using a port if the user does not specify one
- Removed unnecessary reference to RestGSpec from BigDataGSpec
- Completely removed async-http-client to make Rest requests. Now GingerSpec only uses rest-assured internally
- Created a new format to automatically generate features documentation (WIP)
- Added a step for saving the number of rows returned in the last SQL query in a variable for future use in the scenario
- Added a new step to verify the number of rows returned by an SQL query
- ReplacementAspect feature was reorganized and more examples were added
- EnvPropertyLookup can now also read the env variable from a previously saved variable in the same scenario, not only from CLI variables
- GingerSpec now performs variable replacement in the SQL files before executing the query in the database
- Multiples improvements in the rest steps. The method for getting the value of a json element given the jsonpath was modified to use the one that comes pre-bumdled in rest-assured. Several bug fixes and improvements in the log messages when there's an assertion error. Feature for rest steps was revamped with more examples and use cases
2.2.11
- mysql and postgre dependencies were updated and the connection string used to bootstrap the connection no longer uses UTC timezone
- Added new lookup to StringSubstitutor in replacement aspect to evaluate expressions from the Java Faker library
- Fixed an error in which the formatter was unnecessarily calling the replacement aspect. Added a couple of steps for testing how the formatter prints docstring and datatables
- Added a new lookup to StringSubstitutor in replacementAspect to evaluate mathematical expressions using the exp4j library
- Bump log4j-api from 2.14.1 to 2.16.0
- Removed deprecated code from ReplacementAspect, changed its public API method to make it more coherent. Support for !{} #{} and @{} variable placeholders was completely removed from GingerSpec
- Added support to make variable replacements in local files. Now, for example, you can use variables directly in the JSON body of a request that is stored in a local file. GingerSpec will try to perform variable replacement in the text before adding the body to the request. This eliminates the need to use a datatable for altering the body of the request
2.2.10
2.2.9
2.2.8
- Removed some unnecessary classes and methods
- Added new tag @slack that allows sending an slack notification when a scenario fails
- Added ALL and OFF as possible debug level when using tags
- Fixed a bug when creating folder structure when taking an screenshot during selenium tests
Contributors
slack