Juan-A-Jimenez
commented
1 year ago Decisions from the Meeting:
- When definition is always a command: No need for additional Description/Metadata input because only commands can change something in the program
- Given and Then definitions can be determined with the Command (When) node by using sources and target
- Use horizontal lines for test data in YAML
- For now add the Gherkin syntax into the metadata from the feature Element
- The coloring for running, false, successful test can be ignored for now. We still need a way to communicate to the board or another way to solve this.
- The bound context Element needs an entry in the metadata for cody to recognize it as testcase. As fallback the metadata from the feature can have the entry, too. (alternatively) At the moment the root is called "mode":"test"
- We can adjust templates for MetaData input in our Testboard. Actually we should be able to. I just tried and didn't find the configuration. Maybe someone can check this and maybe ask how or why the configuration isn't there.
codeliner
Link to Board: https://app.prooph-board.com/inspectio/board/b13afec8-cb3c-4e4a-b587-9db945a6db3d?cells=jGaiR2bwS37eJ5hv1s6QTF&clicks=1
Idea 1:
Prooph Context Boxfor Testcase Prooph Feature Box for Test Scenario
Look for
GivenNode and all connected EventsWhenNode and all connected CommandThenNode and all expected Data for test assertionsIdea 2:
Prooph Context Box for Test Scenario Propph Feature Box for Given/When/Then
Events in Given will be executed before, commands in When will be executed for test and events/data in Then will be used for test assertions
Idea 3
Prooph Context Boxfor Testcase Prooph Feature Box for Test Scenario
Use horizontal lines for Fiven/When/Then definition. Use information sticky notes to define test data for events/commands and assertion data.