adrhumphreys / fictional-engine Goto Github PK

We have an application which can be interacted with by a user but we’re only testing units and not the application itself

Outcome:

• A users journey is not impacted due to a new change in the codebase

With linting we can pick up on issues that might not be super obvious when implementing our code. By adding it in we hopefully reduce bugs which makes our users happier

Outcome:

• Users see less bugs

This should represent the state when a user first lands in the application, e.g. they haven’t selected any items, set a price, or selected the state code

Outcome:

• The ability to represent the current state of the application

We’ll be creating a react application which will be using typescript

Outcome:

• A user is able to tell that this exists, there’s is something being made

We have an application, but we don’t know if errors are occurring on our users machines, lets ensure we’re monitoring for them

Outcome:

• We’re confident when issues occur in our users browser we record them

We’ve planning to create some functionality, for that we should have testing set up

Outcome:

• A user interacting with the application will not encounter issues

Know we want our users to know what the total price for an order is. We’ll have to apply both the sales tax and the discount rate during this as separating them out into different stories could lead to our users seeing values that don’t represent the actual price)

Outcome:

• Users are able to see the total price

We’ll be updating our state to store a state code which is where the user is making the purchase from:

• We’ll be treating this a non-mandatory field (e.g. they could be making the order outside of these states)
• Ideally this will be easy for a user to select without needing to memorise their state code

Outcome:

• Users are able to update the state to reflect the state they are purchasing their items from

Now that we have the structure documented from Task 1 we can look at creating it in a hardcoded fashion to begin with.

Outcome:

• The ability to fetch/get the data from the dataset

To start with we need to know what the data that we are storing is (this could be in memory/hardcoded or it could be represented later in a database).

Outcome:

• A documented structure for the dataset

We expect our users to see a really high quality application, we want to know when issues occur that affect the visuals of our application

Outcome:

• Users see less visual regressions over time

We’ll be updating our state to store a quantity of items, we’ll need to handle:

• The user is able to input a quantity/price
• The user is able to update a quantity/price
• The user is able to clear a quantity/price

Outcome:

• Users are able to update the state to reflect the quantity of items stored
• Users are able to update the state to reflect the price of the item