Planning (Beta)

[lvanvugt]

Near future planning

1. Get David trained on code **layout/structure/architecture -> DONE

• start today and continue this week
• try to record (for internal use)

2. David can then decide what fits him best and pick that up

• deadline June 15, 2020

3. Luc could than write some specific specifications -> DONE

• Luc will already start to write a first version (of what's already there and is needed still)
• Luc and David sit down to discuss what needs to be specified

Capacity

• Marton has now time to support David's training and review code, not that much at the moment to program
• Programming for now will lean on David
• Luc is acting product owner and will step in from functional side

Next meeting

June 15, 2020

[lvanvugt]

Meeting June 15, 2020

We went through the open issue and prioritized them according to the following list:

• version A: can be picked up right away
• version B: next to be picked up (but needs probably some detailing)
• version C: "for later"

version A

These are now assigned to @DavidFeldhoff, so he can start getting into the code and tooling.

version B

Assigned to @lvanvugt to start writing use case.

Next meeting

June 22, 2020, 10:00

[lvanvugt]

Meeting June 22, 2020

A first part was done: adding given-when-then (#27)

Next meeting in 2 weeks to allow for more room to work on next to other projects

Next meeting

July 13, 2020, 10:00 (moved to July 14)

[lvanvugt]

Meeting July 13, 2020

• smalls steps are being done
• Update Given-When-Then (Use Case: Updating Given-When-Then #30) flowchart has to be updated (not fully clear)

Next meeting

July 20, 2020, 10:00

[lvanvugt]

Meeting July 20, 2020

• @DavidFeldhoff
  • working on back-end service and finished adding, updating and removing GIVEN-WHEN-THEN (scenarios Use Case: Adding Given-When-Then #27, Use Case: Removing Given-When-Then #28, Use Case: Updating Given-When-Then #30)
  • moving part (Use Case: Moving Given-When-Then #29) not yet as it needs an adjustment to the object model
  • provide status update on this issue
• @martonsagi
  • will now pick up UI side of adding, updating and removing GIVEN-WHEN-THEN (scenarios Use Case: Adding Given-When-Then #27, Use Case: Removing Given-When-Then #28, Use Case: Updating Given-When-Then #30) this week
  • adjustment to the object model because of moving part (Use Case: Moving Given-When-Then #29)
• @lvanvugt
  • will start writing SCENARIO and FEATURE scenarios
  • will be on leave end of this week to France, but will available (even though mostly off-line) for testing etc.

Next meeting

August 3, 2020, 10:00

[lvanvugt]

Meeting September 28, 2020

Scenarios #27, #28, #30, #38 and #39 have been implemented.

• @DavidFeldhoff
  • refactored code to replace "C# part"
  • todos
    • fix bugs reported by @lvanvugt
• @martonsagi
  • fix If user does not confirm the update of an element, then the UI does not reset back to the old value. #43 (prio 1)
  • fix Setting maxLengthOfDescription is not taken into account #52 (prio 2)
• @lvanvugt
  • has tested all features so far, based on the 62 ATDD scenarios as defined in atdd-test-scenarios-and-results.xlsx
  • will create bugs for all issues and assign appropriately
  • will continue to define next use cases
    • Updating Scenario
    • Moving Scenario (although this might be for a next version)
    • Adding Feature
    • Renaming Feature
    • Updating Feature
    • Moving Feature (although this might be for a next version)

Goal

The goal for the next period should be to get a beta version out that allows the user to do the most important basic things

• Add, Rename, Update Given/When/Then
• Add, Rename, Update Scenario
• Add, Rename, Update Feature

Anything else is vNext.

Next meeting

October 12, 2020, 08:00, as next week David will be on holidays.

[DavidFeldhoff]

I like reading your summary. Especially the holiday part is music to my ears 😄🙂

[lvanvugt]

Meeting October 26, 2020

• @lvanvugt will test latest changes form @DavidFeldhoff tomorrow

• @martonsagi will fix asap the five issues on his name (in this order please ;-)

  • If user does not confirm the update of an element, then the UI does not reset back to the old value. #43 (Update 20201101: made fix, assigned to @lvanvugt)
  • If a new Scenario is created then the ID 1 is handed over to the backend #44 (Update 20201101: made fix, assigned to @lvanvugt)
  • Add new Scenario -> Add Element -> Error after second scenario #45 (Update 20201101: made fix, assigned to @lvanvugt)
  • Removing Given or Then does not update TestScriptor page #53 (Update 20201101: made fix, assigned to @lvanvugt)
  • Remove Save and Cancel controls from Feature pane #63 (Update 20201101: made fix, assigned to @lvanvugt)

• @DavidFeldhoff continues with

  • Use Case: Adding Scenario #38 (almost finished) (Update 20201101: fix made)
  • Use Case: Removing Scenario #39 (adding settings) (Update 20201101: tested by @lvanvugt and OK)
  • Use Case: Updating Scenario #60 (not yet begun) (Update 20201101: fix made)
  • Use Case: Adding Feature #61 (some already working) (Update 20201101: fix made)
  • Use Case: Removing Feature #62 (but least important) (Update 20201101: fix made)

Goal

The goal is to have half of November to get a beta version out that allows the user to do the most important basic things

• Add, Rename, Update Given/When/Then
• Add, Rename, Update Scenario
• Add, Rename, Update Feature

Extra attention ...

... should be paid to performance.

• How do bigger projects load?
• How about multi-root workspaces?
• UTF-16 encoding is slower that UTF-8!

Next meeting

November 2, 2020, 10:00

[lvanvugt]

Meeting November 2, 2020

(See a number of updates above)

Status

• @martonsagi

  • Use Case: Removing Feature #62
  • Edit Scenario pane: Feature control should be non-editable #69
  • Add new Scenario and click on Scenario title -> ATDD does not jump to the scenario declaration #70
  • Update Scenario -> Confirm? No -> New value is still persisted #71
  • Open ATDD -> Select Scenario with ID -> Select Scenario without ID -> Error "Unexpected type that's modified" #72
  • Select Feature without ID's -> Add new Scenario once (works fine) -> Add new scenario twice (NaN) #73
  • Open ATDD -> Add Scenario -> Always starts with ID 1 (seems it's not initialized) #74

• @lvanvugt

  • retest the whole feature as all known things have been fixed

Goal

The goal is still? to have half of November to get a beta version out that allows the user to do the most important basic things

• Add, Rename, Update Given/When/Then
• Add, Rename, Update Scenario
• Add, Rename, Update Feature

Next meeting

November 9, 2020, 08:00

[lvanvugt]

Meeting November 9, 2020

Status

• @martonsagi; hadn't had time so far to fix the below, but will work on it today (picking up issues reported by @DavidFeldhoff first)

  • Use Case: Removing Feature #62
  • Edit Scenario pane: Feature control should be non-editable #69
  • Add new Scenario and click on Scenario title -> ATDD does not jump to the scenario declaration #70
  • Update Scenario -> Confirm? No -> New value is still persisted #71
  • Open ATDD -> Select Scenario with ID -> Select Scenario without ID -> Error "Unexpected type that's modified" #72
  • Select Feature without ID's -> Add new Scenario once (works fine) -> Add new scenario twice (NaN) #73
  • Open ATDD -> Add Scenario -> Always starts with ID 1 (seems it's not initialized) #74
  • Disable Scenario ID control #75

• @lvanvugt

  • did not start testing yet (due to time shortage)
  • will retest the whole feature after fixes from @martonsagi

• @DavidFeldhoff

  • Disable Scenario ID control #75 (just reported)

Goal

The goal is still to have half of November to get a beta version out that allows the user to do the most important basic things

• Add, Rename, Update Given/When/Then
• Add, Rename, Update Scenario
• Add, Rename, Update Feature

Next meeting

November 16, 2020, 10:00

[lvanvugt]

Meeting November 16, 2020

Status

• @martonsagi

  • has fixed all bugs that were assigned to him
  • had however issue with the loading of TestScriptor page: very slow
    • we all might want to test this using this project https://github.com/dynasist/bc-departments

• @lvanvugt

  • will now start retesting all things
  • will create an icon
    • https://code.visualstudio.com/api/references/extension-manifest

• @DavidFeldhoff

  • pick up bugs returned by @martonsagi

Goal

The goal is still to have half of November to get a beta version out that allows the user to do the most important basic things

• Add, Rename, Update Given/When/Then
• Add, Rename, Update Scenario
• Add, Rename, Update Feature

Next meeting

November 23, 2020, 10:00

[lvanvugt]

Meeting November 23, 2020

Status

• Closed Use Cases

  • Use Case: Adding Given-When-Then #27 (Adding Given-When-Then)
  • Use Case: Removing Given-When-Then #28 (Removing Given-When-Then)
  • Use Case: Adding Scenario #38 (Adding Scenario)
  • Use Case: Removing Scenario #39 (Removing Scenario)

• Open Use Cases

  • Use Case: Updating Given-When-Then #30 (Updating Given-When-Then)
  • Use Case: Updating Scenario #60 (Updating Scenario)
  • Use Case: Adding Feature #61 (Adding Feature)
  • Use Case: Removing Feature #62 (Removing Feature)

• @martonsagi

  • fixed bugs (partly tested and OK)
  • open Update Scenario -> Confirm? No -> New value is still persisted #71, Select Feature without ID's -> Add new Scenario once (works fine) -> Add new scenario twice (NaN) #73, Open ATDD -> Add Scenario -> Always starts with ID 1 (seems it's not initialized) #74
  • other todos
    • adjust build pipeline to enable deployment to VSCode gallary

• @lvanvugt

  • retested and found a number of bugs: Rename of Then goes wrong #79, TestScriptor not updated when removing Scenario from test codeunit with 1 scenario #80, Changing suggested duplicate rename to unique value updates wrong test function/scenario #81
    • meanwhile
      • Rename of Then goes wrong #79 fixed (by @DavidFeldhoff), retested and ok
      • TestScriptor not updated when removing Scenario from test codeunit with 1 scenario #80 closed as cannot be reproduced
  • (temporary) icon created and made part of build
  • to be tested: Rename when Given/When/Then helper function do not follow settings prefix #51, Make Feature-Tag optionally #78
  • other to dos:
    • create readme and changelog

• @DavidFeldhoff

  • picked up bugs returned by @martonsagi
  • open Changing suggested duplicate rename to unique value updates wrong test function/scenario #81

Goal

The goal (updated) is still to have half of November to get a beta version out that allows the user to do the most important basic things

• Add, Update, Remove Given/When/Then
• Add, Update, Remove Scenario
• Add, Update, Remove Feature

Next meeting

November 30, 2020, 10:00

[lvanvugt]

Meeting November 30, 2020

Status

• Closed Use Cases

  • Use Case: Adding Given-When-Then #27 (Adding Given-When-Then)
  • Use Case: Removing Given-When-Then #28 (Removing Given-When-Then)
  • Use Case: Updating Given-When-Then #30 (Updating Given-When-Then)
  • Use Case: Adding Scenario #38 (Adding Scenario)
  • Use Case: Removing Scenario #39 (Removing Scenario)

• Open Use Cases

  • Use Case: Updating Scenario #60 (Updating Scenario)
  • Use Case: Adding Feature #61 (Adding Feature)
  • Use Case: Removing Feature #62 (Removing Feature)

• @martonsagi

  • open Update Scenario -> Confirm? No -> New value is still persisted #71, Select Feature without ID's -> Add new Scenario once (works fine) -> Add new scenario twice (NaN) #73, Open ATDD -> Add Scenario -> Always starts with ID 1 (seems it's not initialized) #74
  • other todos
    • adjust build pipeline to enable deployment to VSCode gallery

• @lvanvugt

  • created (first version of) readme and changelog
  • tested: Rename when Given/When/Then helper function do not follow settings prefix #51
  • to be tested: Make Feature-Tag optionally #78

• @DavidFeldhoff

  • open Changing suggested duplicate rename to unique value updates wrong test function/scenario #81

Goal

The goal (updated) was to have half of November to get a beta version out that allows the user to do the most important basic things

• Add, Update, Remove Given/When/Then
• Add, Update, Remove Scenario
• Add, Update, Remove Feature

Next meeting

December 7, 2020, xxxx

[lvanvugt]

Status December 28, 2020 January 21,2021

• Closed Use Cases

  • Use Case: Adding Given-When-Then #27 (Adding Given-When-Then)
  • Use Case: Removing Given-When-Then #28 (Removing Given-When-Then)
  • Use Case: Updating Given-When-Then #30 (Updating Given-When-Then)
  • Use Case: Adding Scenario #38 (Adding Scenario)
  • Use Case: Removing Scenario #39 (Removing Scenario)

• Open Use Cases

  • Use Case: Updating Scenario #60 (Updating Scenario)
  • Use Case: Adding Feature #61 (Adding Feature)
  • Use Case: Removing Feature #62 (Removing Feature)

• @martonsagi

  • open Use Case: Adding Feature #61, Use Case: Removing Feature #62 help wanted (maybe already fixed?)
  • open Update Scenario -> Confirm? No -> New value is still persisted #71 (20210121)

• @lvanvugt

  • to be tested: Make Feature-Tag optionally #78, Changing suggested duplicate rename to unique value updates wrong test function/scenario #81
  • closed: Changing suggested duplicate rename to unique value updates wrong test function/scenario #81 (20210121)

• @DavidFeldhoff

  • open Update Scenario -> Confirm? No -> New value is still persisted #71
  • open: Make Feature-Tag optionally #78 help wanted (20210121)
  • closed Select Feature without ID's -> Add new Scenario once (works fine) -> Add new scenario twice (NaN) #73, Open ATDD -> Add Scenario -> Always starts with ID 1 (seems it's not initialized) #74 (20210121)

Goal

The goal (updated) was to have half of November to get a beta version out that allows the user to do the most important basic things

• Add, Update, Remove Given/When/Then
• Add, Update, Remove Scenario
• Add, Update, Remove Feature

[lvanvugt]

Meeting January 21, 2021

Status

See previous post

Remaining to-dos

• @martonsagi
  • Use Case: Adding Feature #61, Use Case: Removing Feature #62 Update Scenario -> Confirm? No -> New value is still persisted #71 (high prio)
    • get these fixed/completed before next meeting (see below)
  • enable pipeline to release to VSCode Marketplace
• @DavidFeldhoff and @lvanvugt
  • Make Feature-Tag optionally #78 (low prio)
    • get test scenarios in place

Automated tests

@DavidFeldhoff has scripted test to test the back-end, but was not (yet) able to incorporate them (so they would run) in the pipeline. @martonsagi will see, once all the above is ready, if he can get it working in the pipeline.

Goal

The goal (updated) was to have half of November to get a beta version out that allows the user to do the most important basic things

• Add, Update, Remove Given/When/Then
• Add, Update, Remove Scenario
• Add, Update, Remove Feature

Next meeting

January 28, 2021, 08:00 (AM)

[lvanvugt]

Meeting January 28, 2021

Status

• @martonsagi
  • fixed Use Case: Adding Feature #61, Use Case: Removing Feature #62, Update Scenario -> Confirm? No -> New value is still persisted #71
  • release pipeline to marketplace
• @DavidFeldhoff
  • not yet fully fixed Make Feature-Tag optionally #78
  • create issues for
    • codeunits that do not have FEATURE/SCENARIO tags will be displayed in TestScriptor based on the test method name (Is already implemented but should be documented)
    • casting long SCENARIO description into test method name
• @lvanvugt
  • will need to retest all
  • create use case(s) for next release on handling FEATURE tags:
    • split codeunit with x FEATUREs into codeunits for each tag, i.e. being x codeunits (Use Case Use Case: Handle multiple Features in one test codeunit #84)
    • 1 FEATURE distributed over multiple codeunits (Use Case Use Case: Handle one Feature spread over multiple test codeunits #85)

Goal

The goal (updated) was to have half of November to get a beta version out that allows the user to do the most important basic things

• Add, Update, Remove Given/When/Then
• Add, Update, Remove Scenario
• Add, Update, Remove Feature

Next meeting

February 4, 2021, 08:00 (AM)

[lvanvugt]

Status January 30,2021

• Closed Use Cases
  • Use Case: Adding Given-When-Then #27 (Adding Given-When-Then)
  • Use Case: Updating Given-When-Then #30 (Updating Given-When-Then)
  • Use Case: Adding Scenario #38 (Adding Scenario)
  • Use Case: Updating Scenario #60 (Updating Scenario)
• Open Use Cases
  • reopened Use Case: Removing Given-When-Then #28 (Removing Given-When-Then) -> bug Clicking second time on garbage can while not having approved first time #86
  • reopened Use Case: Removing Scenario #39 (Removing Scenario) -> bug Clicking second time on "Delete Scenario" action while not having approved first time #88
  • Use Case: Adding Feature #61 (Adding Feature) -> bug Adding duplicate feature should throw message and revert addition in TestScriptor page #87
  • Use Case: Removing Feature #62 (Removing Feature) -> not working (see notes on Use Case itself)

Scope extension

• could we add Update TestScriptor page when manually adding a GIVEN/THEN #48 in some way to allow the user to refresh the TestScriptor page somehow?

[lvanvugt]

Meeting February 4, 2021

Status

• @martonsagi
  • fixed release pipeline to marketplace
  • to fix
    • Use Case: Removing Given-When-Then #28 (Removing Given-When-Then) / bug Clicking second time on garbage can while not having approved first time #86
    • Use Case: Removing Scenario #39 (Removing Scenario) / bug Clicking second time on "Delete Scenario" action while not having approved first time #88
• @DavidFeldhoff
  • create issues for
    • codeunits that do not have FEATURE/SCENARIO tags will be displayed in TestScriptor based on the test method name (Is already implemented but should be documented)
    • casting long SCENARIO description into test method name
  • find a fix for issue Test Scenario Editor wont show when using custom testDirectory #89, reported by Stefan Maron
  • working on Use Case: Removing Feature #62 (Removing Feature)
  • fixed locally Use Case: Adding Feature #61 (Adding Feature)/bug Adding duplicate feature should throw message and revert addition in TestScriptor page #87 -> needs to be pushed to GitHub
• @lvanvugt
  • retested all and reported issues (see above Status January 30,2021)
  • updated READ.ME to contain more/better info and two videos
  • handed over a beta build .vsix to Stefan Maron
  • define VSCE_PAT variable that is an access token for your Marketplace account VSCE_PAT variable access token Marketplace #90
  • define Azure blob storage to hold an insider .vsix build Azure BLOB storage for insider build #91

Goal

To get a beta version out that allows the user to do the most important basic things

• Add, Update, Remove Given/When/Then
• Add, Update, Remove Scenario
• Add, Update, Remove Feature

Next meeting

February 9, 2021, 08:00 (AM)

[lvanvugt]

Meeting February 9, 2021

Status

• @martonsagi
  • fixed
    • Use Case: Removing Given-When-Then #28 (Removing Given-When-Then) / bug Clicking second time on garbage can while not having approved first time #86
    • Use Case: Removing Scenario #39 (Removing Scenario) / bug Clicking second time on "Delete Scenario" action while not having approved first time #88
    • New Feature in empty project not possible #94 reported by Stefan Maron (works fine in single project workspace, not in multi project one - and we did not tests that any way)
    • When just moving out of Feature name box (in Features pane) a rename is triggered. Needs to be fixed (@DavidFeldhoff will create issue)
• @DavidFeldhoff
  • fixed Test Scenario Editor wont show when using custom testDirectory #89, reported by Stefan Maron
  • create issues for
    • codeunits that do not have FEATURE/SCENARIO tags will be displayed in TestScriptor based on the test method name (Is already implemented but should be documented) -> DONE If a scenario tag is missing of a test method, then the method name should be taken into account. #93 (and closed as it was already fixed)
    • casting long SCENARIO description into test method name
  • working on Use Case: Removing Feature #62 (Removing Feature) -> see Luc's note as it seems not to be complete
  • fixed locally Use Case: Adding Feature #61 (Adding Feature)/bug Adding duplicate feature should throw message and revert addition in TestScriptor page #87 -> Still open question from @martonsagi
  • to fix Suggestion: lesser dialogs popping up when renaming  #95
• @lvanvugt
  • handed over a beta build .vsix to Stefan Maron
  • define VSCE_PAT variable that is an access token for your Marketplace account VSCE_PAT variable access token Marketplace #90 -> DONE
  • define Azure blob storage to hold an insider .vsix build Azure BLOB storage for insider build #91 -> provided Access Key url
  • document in READ.ME that multi-project workspace has not yet been tested/supported

Goal

To get a beta version out that allows the user to do the most important basic things

• Add, Update, Remove Given/When/Then
• Add, Update, Remove Scenario
• Add, Update, Remove Feature

Next meeting

February 18, 2021, 16:00 (AM)

[lvanvugt]

Status February 18,2021

• Closed Use Cases
  • Use Case: Adding Given-When-Then #27 (Adding Given-When-Then)
  • Use Case: Removing Given-When-Then #28 (Removing Given-When-Then)
  • Use Case: Updating Given-When-Then #30 (Updating Given-When-Then)
  • Use Case: Adding Scenario #38 (Adding Scenario)
  • Use Case: Removing Scenario #39 (Removing Scenario)
  • Use Case: Updating Scenario #60 (Updating Scenario)
• Open Use Cases
  • Use Case: Adding Feature #61 (Adding Feature) -> bug Adding duplicate feature should throw message and revert addition in TestScriptor page #87
  • Use Case: Removing Feature #62 (Removing Feature) -> still not working well (see notes on Use Case itself)

Scope extension

• could we add Update TestScriptor page when manually adding a GIVEN/THEN #48 in some way to allow the user to refresh the TestScriptor page somehow? help wanted @martonsagi

[lvanvugt]

Meeting February 18, 2021

Status

• @martonsagi
  • to fix Suggestion: lesser dialogs popping up when renaming  #95
  • Use Case: Adding Feature #61 (Adding Feature)/bug Adding duplicate feature should throw message and revert addition in TestScriptor page #87 -> Still open question from @martonsagi
  • Also when just moving out of Feature name box (in Features pane) a rename is triggered. Needs to be fixed (@DavidFeldhoff will create issue)
• @DavidFeldhoff
  • create issue for
    • casting long SCENARIO description into test method name
  • open
    • Use Case: Removing Feature #62 (Removing Feature)
    • Use Case: Adding Feature #61 (Adding Feature)/bug Adding duplicate feature should throw message and revert addition in TestScriptor page #87 -> Still open question from @martonsagi
  • to fix Suggestion: lesser dialogs popping up when renaming  #95
• @lvanvugt
  • define Azure blob storage to hold an insider .vsix build Azure BLOB storage for insider build #91 -> provided Access Key url
    • help needed from @martonsagi
  • updated READ.ME

Goal

To get a beta version out that allows the user to do the most important basic things

• Add, Update, Remove Given/When/Then
• Add, Update, Remove Scenario
• Add, Update, Remove Feature

Next meeting

February 25, 2021, 16:00 (AM)

[lvanvugt]

Meeting February 25, 2021

Status

• @martonsagi
  • to fix Suggestion: lesser dialogs popping up when renaming  #95
  • Use Case: Adding Feature #61 (Adding Feature)/bug Adding duplicate feature should throw message and revert addition in TestScriptor page #87 -> Still open question from @martonsagi
  • Also when just moving out of Feature name box (in Features pane) a rename is triggered. Needs to be fixed (@DavidFeldhoff will create issue)
• @DavidFeldhoff
  • create issue for
    • casting long SCENARIO description into test method name
  • open
    • Use Case: Removing Feature #62 (Removing Feature)
    • Use Case: Adding Feature #61 (Adding Feature)/bug Adding duplicate feature should throw message and revert addition in TestScriptor page #87 -> Still open question from @martonsagi
  • to fix Suggestion: lesser dialogs popping up when renaming  #95
• @lvanvugt
  • with help of @martonsagi DONE Azure blob storage to hold an insider .vsix build Azure BLOB storage for insider build #91
    • https://luxadofiles.blob.core.windows.net/atddtestscriptorinsiderbuild/latest-develop.vsix
    • and tried to have pipeline release to VSCode Marketplace (latter is not yet fully working the tagging does work)
      • we might try with the newer PAT (Luc wil do)
  • updated READ.ME
  • tested "Feature in multiple files error" while renaming a scenario #98 and OK

Goal

To get a beta version out that allows the user to do the most important basic things

• Add, Update, Remove Given/When/Then
• Add, Update, Remove Scenario
• Add, Update, Remove Feature

Next meeting

March 11, 2021, 17:30 (AM)

[lvanvugt]

Meeting March 11, 2021

@lvanvugt forgotten to update the notes.

Goal

To get a beta version out that allows the user to do the most important basic things

• Add, Update, Remove Given/When/Then
• Add, Update, Remove Scenario
• Add, Update, Remove Feature

Next meeting

March 19, 2021, 16:30 (AM)

[lvanvugt]

Meeting March 19, 2021

Status

• Closed Use Cases

  • Use Case: Adding Given-When-Then #27 (Adding Given-When-Then)
  • Use Case: Removing Given-When-Then #28 (Removing Given-When-Then)
  • Use Case: Updating Given-When-Then #30 (Updating Given-When-Then)
  • Use Case: Adding Scenario #38 (Adding Scenario)
  • Use Case: Removing Scenario #39 (Removing Scenario)
  • Use Case: Updating Scenario #60 (Updating Scenario)
  • Use Case: Removing Feature #62 (Removing Feature)

• Open Use Cases

  • Use Case: Adding Feature #61 (Adding Feature) -> bug Adding duplicate feature should throw message and revert addition in TestScriptor page #87

• @martonsagi

  • open
    • Adding duplicate feature should throw message and revert addition in TestScriptor page #87
    • "Unable to rename feature" appears when I'm clicking through the features even without I'm changing something #100
    • with @DavidFeldhoff
      • Suggestion: lesser dialogs popping up when renaming  #95
      • Empty Feature is created #96

• @DavidFeldhoff

  • open
    • Use Case: Adding Feature #61
    • with @martonsagi
      • Suggestion: lesser dialogs popping up when renaming  #95
      • Empty Feature is created #96

• @lvanvugt

  • with help of @martonsagi have pipeline release to VSCode Marketplace working
  • tested Use Case: Removing Feature #62 and OK
  • officially announced this release: https://twitter.com/lucvanvugt/status/1372877744112013312

Goal

To get a beta version out that allows the user to do the most important basic things

• Add, Update, Remove Given/When/Then
• Add, Update, Remove Scenario
• Add, Update, Remove Feature

Next meeting

March 25, 2021, 16:30 (AM)

[lvanvugt]

Meeting March 25, 2021

Nothing achieved last week.

Goal

To get a beta version out that allows the user to do the most important basic things

• Add, Update, Remove Given/When/Then
• Add, Update, Remove Scenario
• Add, Update, Remove Feature

Next meeting

April 1, 2021, 16:30 (AM)

[lvanvugt]

Meeting April 1, 2021

Status

• Closed Use Cases

  • Use Case: Adding Given-When-Then #27 (Adding Given-When-Then)
  • Use Case: Removing Given-When-Then #28 (Removing Given-When-Then)
  • Use Case: Updating Given-When-Then #30 (Updating Given-When-Then)
  • Use Case: Adding Scenario #38 (Adding Scenario)
  • Use Case: Removing Scenario #39 (Removing Scenario)
  • Use Case: Updating Scenario #60 (Updating Scenario)
  • Use Case: Removing Feature #62 (Removing Feature)
  • Use Case: Adding Feature #61 (Adding Feature)

• @martonsagi

  • open
    • Adding duplicate feature should throw message and revert addition in TestScriptor page #87
  • closed
    • "Unable to rename feature" appears when I'm clicking through the features even without I'm changing something #100

• @DavidFeldhoff

  • open
    • Suggestion: lesser dialogs popping up when renaming  #95
    • Changing the when element fails some times #101
    • Add a new feature should also work in multiroot workspaces. #102
  • closed
    • Empty Feature is created #96

• @lvanvugt

  • groom the backlog on next version use cases

Goal

To get a beta version out that allows the user to do the most important basic things

• Add, Update, Remove Given/When/Then
• Add, Update, Remove Scenario
• Add, Update, Remove Feature

Next meeting

April 8, 2021, 16:30 (AM)

[lvanvugt]

Meeting April 8, 2021

We're close to completing beta and set version to 1!

Status

• Closed Use Cases

  • Use Case: Adding Given-When-Then #27 (Adding Given-When-Then)
  • Use Case: Removing Given-When-Then #28 (Removing Given-When-Then)
  • Use Case: Updating Given-When-Then #30 (Updating Given-When-Then)
  • Use Case: Adding Scenario #38 (Adding Scenario)
  • Use Case: Removing Scenario #39 (Removing Scenario)
  • Use Case: Updating Scenario #60 (Updating Scenario)
  • Use Case: Removing Feature #62 (Removing Feature)
  • Use Case: Adding Feature #61 (Adding Feature)

• @martonsagi

  • open
    • Adding duplicate feature should throw message and revert addition in TestScriptor page #87

• @lvanvugt

  • to be tested
    • Suggestion: lesser dialogs popping up when renaming  #95
    • Empty Feature is created #96
    • Scenarios shown multiple times in workspaces #99
    • Changing the when element fails some times #101
    • Add a new feature should also work in multiroot workspaces. #102

Goal

To get a beta version out that allows the user to do the most important basic things

• Add, Update, Remove Given/When/Then
• Add, Update, Remove Scenario
• Add, Update, Remove Feature

Next meeting

Not set yet. Let's complete the above and release as v1. Once done we'll have a next call.

[lvanvugt]

v1 is now being picked up. Planning is now to be found in #111.