After a very long period of silence today we had a re-kickoff call with @martonsagi, @DavidFeldhoff and @lvanvugt. Goal was to brainstorm on where we (think we) are and where we want to move to.
Based on the brain varts of each we have come to the following "plan":
- Get an understanding of what the current status of the ATDD.TestScriptor is
- Determine what needs to be done to get a stable version (v1) out
- Define scope of v2, which could
- Excel import (create code from Excel file like ATDD.TestScriptor PowerShell module is doing right now)
- Simple Excel export that abstracts ATDD meta data from code
- v2 should not yet enable sync between Excel and code, but should also not block this in future
- Excel sync would be something for v3
Next
To determine what is needed to get v1 completed we will have a demo session on November 27, 2022, 10AM.
At the end of this session a pair-programming session will be planned by @martonsagi and @DavidFeldhoff
Focus:
- automated tests
- clear picture of current architecture (would be great is we have a schema for this)
Note
With this we close the beta phase #22.
After a very long period of silence today we had a re-kickoff call with @martonsagi, @DavidFeldhoff and @lvanvugt. Goal was to brainstorm on where we (think we) are and where we want to move to.
Based on the brain varts of each we have come to the following "plan":
Next
To determine what is needed to get v1 completed we will have a demo session on November 27, 2022, 10AM.
At the end of this session a pair-programming session will be planned by @martonsagi and @DavidFeldhoff
Focus:
Note
With this we close the beta phase #22.