You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to acquire acceptance-integration tests a Behaviour-driven development tool could be used. The support of multitenancy could complicate development and the use of feature testing could help on keeping features clean.
Tools
Cucumber could be used as it integrates well with Spring and could help translate requirements to Gherkin-language tests.
Sure. Before providing any implementation , do some research and understand the existing flows the CMS is supporting. Then you can propose how our tool could benefit from BDD by providing specific examples, so we can discuss them. If it is easy for you we can do it directly on a PR.
Purpose
In order to acquire acceptance-integration tests a Behaviour-driven development tool could be used. The support of multitenancy could complicate development and the use of feature testing could help on keeping features clean.
Tools
Cucumber could be used as it integrates well with Spring and could help translate requirements to Gherkin-language tests.
Resources
https://cucumber.io
https://cucumber.io/docs/cucumber/state/
If this is desirable I could work on that and submit a Pull Request.
The text was updated successfully, but these errors were encountered: