On 2 Nov 2020, at 08:45, David Shavit <shavi...@gmail.com> wrote:
--
You received this message because you are subscribed to the Google Groups "Behaviour Driven Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to behaviordrivendeve...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/behaviordrivendevelopment/adb8a3f7-fd76-4428-bdb3-7a1beaf142b0n%40googlegroups.com.
Scenario: Playback mode – login process with data files in the library
Given there are the following drives: 'X:, C:'
And under drive 'X:' there are the following projects: 'A,B'
And under project 'G280' there are the following A/C: '88,89'
And under A/C '2001' there are the following TSN/FLT: '"FL002/TSN009","FL003/TSN011"'
And under TSN/FLT '"FL002/TSN009"' there are the following Format: 'PCM1,PCM2'
And TSN/FLT '"FL002/TSN009"'contains the following run numbers '300, 310, 320'
And run number '300' connected to layout file 'Test Name 01'
And run number '310' connected to layout file 'Test Name 02'
And run number '320' connected to layout file 'Test Name 01'
And under Format 'PCM1' there are the following Files and options: '"Rdf_A_009_PCM1_F002_MAIN_20032015_A", "Rdf_A_009_PCM1_F002_MAIN_20032015_B", 'choose another file''
And under File '"Rdf_B_009_PCM1_F002_MAIN_20032015_A"' there are the following Sample rate options: '"60", "300", "10"'
And under File '"Rdf_B_009_PCM1_F002_MAIN_20032015_A"' there are the following Audio: '"None", "Combine", "Audio Only"'
And under File '"Rdf_B_009_PCM1_F002_MAIN_20032015_A"' there are the following exercises taken '"300-A", "300-B", "310-A"'
When the FTE selects in field 'mode' the value 'Playback'
And selects in field 'drive' the value 'X:'
And selects in field 'project' the value 'A'
And selects in field 'A/C' the value '88'
And selects in field 'TSN/FLT' the value 'FL002/TSN009'
And selects in field 'Format' the value 'PCM1'
And selects in field 'File' the value ' Rdf_A_009_PCM1_F002_MAIN_20032015_A '
And selects in field 'Audio' the value 'Combine'
And The FTE presses “login”
Then the options selected in fields 'mode', 'drive', 'project', 'A/C', 'TSN/FLT', 'Format' are saved for the next entry
And the options selected in fields 'File', 'Audio' are not saved for the next entry
And The FTE continues to the Playback main screen
And the "Playback timeline" is displayed
And the actual run number is the first run number in the rdf or ethernet file
And the screen file of the actual run number is displayed on the canvas
And the actual run number is marked on the "Playback timeline"
And the actual first exercise in the rdf or ethernet file is displayed on the canvas
And the actual first exercise in the rdf or ethernet file is marked on the "Playback timeline"
And the "exercise running toolbar" is enabled
And the "player toolbar" is enabled
And "Generals" tab is enabled
And the "Go to exercise" tab is enabled
And "Flight and test run data" is displayed
And the 'Test Name' is displayed
And the "SETTINS" tab is enabled
And the "EXERCISE" tab is enabled
And the VIEW tab is enabled
And the FILE tab is displayed as BUILDER
And the BUILDER tab is enabled
And the ELEMENTS tab is enabled
And data is displayed on all the elements in the screen
--
You received this message because you are subscribed to the Google Groups "Behaviour Driven Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to behaviordrivendeve...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/behaviordrivendevelopment/074a9f5d-fe77-44b1-aa70-d58bc3112705n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/behaviordrivendevelopment/a6c533e4-21e8-4336-979f-b15e68c71936n%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Behaviour Driven Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to behaviordrivendeve...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/behaviordrivendevelopment/e05b4b2a-90ce-4eb5-a5c2-467ab8249936n%40googlegroups.com.
Given a drive X with projects A and B
Given A has A/C: 88, 89
And other projects and A/C also exist
Given Format 'PCM1' has a file dated 20032015
And that file contains Sample rate options "60", "300", "10"
And Audio options "None", "Combine", "Audio only"
And Exercises "300-A", "300-B", "310-A"
When the FTE selects mode "Playback", drive "X" and project "A"
And also selects A/C "88", field "TSN/FLT" and value "FL002/TSN009"
And also selects...
Given the FTE has selected "Playback" mode (etc.)When they loginThen the Audio, Exercises, A/C and Wibble fields should be visible and enabled
And the fields should have appropriate values
--
You received this message because you are subscribed to the Google Groups "Behaviour Driven Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to behaviordrivendeve...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/behaviordrivendevelopment/074a9f5d-fe77-44b1-aa70-d58bc3112705n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/behaviordrivendevelopment/dd85d6aa-0224-4f22-a3a8-b399f9a69b5dn%40googlegroups.com.
BSD
Hello everyone
First I want to say that this is my first topic here in the forum, I have to admit that I a bit surprise from the high level responses
It seem that beside the fact that the authors here are highly professional there is noticeable unique spirit for sharing how to do things right and more accurate and that should be admired, So Thanks a lot!
I just want to summarize what i have learned on this topic. I got a lot of insights. Some of them focused on the BDD`s philosophy and other important general ideas other were more specific about how to write more readable specs and how to do the distinguish between details and the major route, so these most of the insights:
1. Use the language and terms used by the domain experts
2. sniff around them when they are alone to find their exact business terms
3. when neglecting the domain language the specs disconnect each other
4. Inevitably the spec should focus on the gui when it`s the current domain
5. it is necessary to understand what is the purposes and goals we want to achieve which the scenarios will describe
6. the main goals of bdd is to communicate within the whole disciplines , document in story manner, and validate it against the system developed
7. indication that the scenario is not in correct story manner it cannot be repeated by one of the team mates
8. bad practice is when scenario look more like test script and less like a well-documented and interesting story to tell some team mate
9. unreadable scenarios led to lose the motivation to read and maintain the scenarios.
10. indication of well written scenario is when it cause questions to pop-up
11. Login window isn`t system function unless it determine who can get authorize to data and what kind of data to access.
12. Scenario should split thus handling one issue each time
13. mention only must-have details on your scenario, those that influence the expected outcome
14. Login window should have sad path either
15. scenario should describe the WHAT instead of the HOW aspect. The WHAT part usually expressed in the WHEN gherkin's phase
16. considering login window then entering user name and password belongs to the HOW aspect
17. BDD scenarios main purpose is dealing with the WHAT from high level view, drive the dev team toward desired behavior.
18. specs aren't the right place for details. The details lays in the application itself, like Map which describe the territory.
19. Like as a map the scenarios are only entry point for digging the territory.
20. Scenario like continue to be updated because it coupled with the current code.
21. Scenario happy path should be written using three line`s spec
22. One of the challenges to write the scenario is to find the accurate words which making complex matter to light heavy one
23. Good practice is to hide the over details into the code
24. Use background to avoid duplicating
25. Comparing scenario helps to identify the details they don`t matter to specific behavior
26. Constant conditions should be mentioned shortly i.e. this matter is in "appropriate manner"
27. There should be thinking about what is the correct domain. GUI itself sometimes is the correct domain.
28. Record and playback testing pros and cons
Thank you all, this conversation has tremendous value for my retrospective and I'm sure it`s will be for future readers
I`ll we be happy to read your opinions on the next retrospective issues
David