Create a Receipt

[Norbbs]

As a User
I want to create and save a recipe
So that I can easily access and prepare my favorite dishes.

Definition Of Ready (DoR)

	Definition	Observations
	The story meet the INVEST and SMART criteria
	Dependencies identified and resolved
	Written acceptance criteria with test scenarios, understood by the team and agreed upon
	The user story was understood and agreed upon in a refinement session with the dev team
	The team has an idea of how to make the demonstration of the finished story

Scope

1. Create data in the entity recipe_levels:

Property	Key	Type	Nullable	Limit	Example
id	PRIMARY	INTEGER	NOT NULL	AUTO INCREMENT	1
description	UNIQUE	TEXT	NOT NULL	12	Easy

2. Create data in the entity recipe_types:

Property	Key	Type	Nullable	Limit	Example
id	PRIMARY	INTEGER	NOT NULL	AUTO INCREMENT	1
description	UNIQUE	TEXT	NOT NULL	50	Chilean Food

3. Create data in the entity recipe_status:

Property	Key	Type	Nullable	Limit	Example
id	PRIMARY	INTEGER	NOT NULL	AUTO INCREMENT	1
description	UNIQUE	TEXT	NOT NULL	50	Approved
is_active		TINYINT		NOT NULL	1

4. Create data in the entity recipes:

Property	Key	Type	Nullable	Limit	Example
id	PRIMARY	INTEGER	NOT NULL	AUTO INCREMENT	1
title	UNIQUE	TEXT	NOT NULL	50	Queque de lima y limón
type_id	FOREIGN	INTEGER	NOT NULL	recipe_types	1
level_id	FOREIGN	INTEGER	NOT NULL	recipe_levels	1
preparation_time		TINYINT		UNSIGNED	90
uom_time_id	MS	INTEGER		TOPH	11
uom_time_abbreviation	MS	TEXT(5)		TOPH	min
persons_qty		INTEGER			5
status_id		TINYINT	NOT NULL	recipe_status	1

5. Create data in the entity recipe_media_types:

Property	Key	Type	Nullable	Limit	Example
id	PRIMARY	INTEGER	NOT NULL	AUTO INCREMENT	1
description	UNIQUE	TEXT	NOT NULL	12	Image

6. Create data in the entity recipe_media_sources:

Property	Key	Type	Nullable	Limit	Example
id	PRIMARY	INTEGER	NOT NULL	AUTO INCREMENT	1
description	UNIQUE	TEXT	NOT NULL	30	youtube

7. Create data in the entity recipes_media:

Property	Key	Type	Nullable	Limit	Example
id	PRIMARY	INTEGER	NOT NULL	AUTO INCREMENT	1
recipe_id	FOREIGN	INTEGER	NOT NULL	recipes	1
type_id	FOREIGN	INTEGER	NOT NULL	recipe_media_types	1
source_id	FOREIGN	INTEGER	NOT NULL	recipe_media_sources	1
media_url		TEXT		250	https://youtube.com/watch?v=example123
media_blob		BYTEA			0x89504E470D0A1A0A
is_main		TINYINT	NOT NULL		1

Out of scope

1. update, delete and other non-creation processes.
2. ingredients or other non-recipe entity are out of scope.

Acceptance Criteria

		AC	GIVEN	WHEN	THEN
	1	Create a recipe successfully	a recipe title	the recipe creation process is triggered	the recipe will be created in the table recipes.
	2	Create a recipe with image successfully	a recipe title and an image	the recipe creation process is triggered	the recipe will be created in the table recipes with the title and data in the image field.
	3	Don't create a recipe because of data duplication	a recipe title and our database has one recipe with the SAME title	the recipe creation process is triggered	the recipe WON'T be created in the table recipes.
	4	Don't create a recipe because of data mutually exclusive	a recipe title, an quantity but WITHOUT uom	the recipe creation process is triggered	the recipe WON'T be created in the table recipes.
	5	Don't create a recipe because of data mutually exclusive	a recipe title, an oum but WITHOUT quantity	the recipe creation process is triggered	the recipe WON'T be created in the table recipes.
	6	Don't create a recipe because of quantity is less than or equal to zero	a recipe title, a quantity is less than or equal to zero	the recipe creation process is triggered	the recipe WON'T be created in the table recipes.
	7	Don't create a recipe because of uom is not a time unit	a recipe title, quantity and uom which is not a time unit	the recipe creation process is triggered	the recipe WON'T be created in the table recipes.
	8	Create a recipe with title, quantity and uom (time) correctly	a recipe title, quantity and uom (time unit)	the recipe creation process is triggered	the recipe will be created in the table recipes.

Definition of Done (DoD)

	Definition	Result
	All acceptance criteria have been met
	No significant or critical defects
	Deskcheck ceremony has been made
	Keep minimum test coverage of 80% over the necessary code and components
	Technical documentation published
	Spike, PoC or benchmarks findings documented