Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Planning v1 #111

Open
lvanvugt opened this issue Oct 14, 2022 · 10 comments
Open

Planning v1 #111

lvanvugt opened this issue Oct 14, 2022 · 10 comments
Assignees
Labels
version A To be picked up right away
Milestone

Comments

@lvanvugt
Copy link
Contributor

lvanvugt commented Oct 14, 2022

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":

  1. Get an understanding of what the current status of the ATDD.TestScriptor is
  2. Determine what needs to be done to get a stable version (v1) out
  3. 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
  4. 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.

@lvanvugt lvanvugt added the version A To be picked up right away label Oct 14, 2022
@lvanvugt lvanvugt self-assigned this Oct 14, 2022
@lvanvugt
Copy link
Contributor Author

lvanvugt commented Nov 27, 2022

Meeting November 27, 2022

We discussed that status of the product by means of the investigation @lvanvugt and record it in #114. In this we focussed on the bugs. These will be our first focus (from top to bottom).

Status

Bugs

Goal

We are targetting to get these fixed before 31st of January 2023. After that we are going to pick up the in-scope enhancements.

Next meeting

December 8, 2022, 08:00.

@lvanvugt
Copy link
Contributor Author

lvanvugt commented Dec 22, 2022

Meeting December 22, 2022

Status

Solved

Needs testing

Open (bugs)

New

Goal

We are still targetting to get these fixed before 31st of January 2023. After that we are going to pick up the in-scope enhancements.

Test automation

@DavidFeldhoff and @lvanvugt will sit down on January 18, 2023 (17:00) to discuss what ATDD tests could be implemented as backend tests.

Next meeting

January 12 19, 2023, 08:00.

@lvanvugt
Copy link
Contributor Author

lvanvugt commented Jan 19, 2023

Meeting January 19, 2023

  • waiting for @lvanvugt to handle testing; has blocked January 23 and 30 for it
  • @DavidFeldhoff and @lvanvugt had first meeting on test automation of our code; to be continued
  • ...

Status

Needs testing

Open (bugs)

In progress

Goal

We are still targetting to get these fixed before 31st of January 2023. After that we are going to pick up the in-scope enhancements.

Next meeting

February 1, 2023, 08:00.

@lvanvugt
Copy link
Contributor Author

lvanvugt commented Jan 23, 2023

@lvanvugt
Copy link
Contributor Author

lvanvugt commented Feb 14, 2023

@lvanvugt
Copy link
Contributor Author

lvanvugt commented Feb 17, 2023

Meeting March 7 9, 2023

Status

Needs testing

Open (bugs)

In progress

Completed

Goal

We are still targetting to get these fixed before 31st of March 2023 (skipped from 31st of January). After that we are going to pick up the in-scope enhancements.

Next meeting

March 24, 2023, 08:00.

@lvanvugt lvanvugt added this to the v1 milestone Feb 18, 2023
@lvanvugt
Copy link
Contributor Author

lvanvugt commented Mar 24, 2023

Meeting March 22 24, 2023

Status

Needs testing

Open (bugs)

In progress

Completed

Goal

We are still targetting to get these fixed before 31st of March 2023 (skipped from 31st of January). After that we are going to pick up the in-scope enhancements.

Next meeting

March 31, 2023, 08:00.

@lvanvugt
Copy link
Contributor Author

lvanvugt commented Mar 31, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
version A To be picked up right away
Projects
None yet
Development

No branches or pull requests

1 participant