split part 8-11

07 Frequently Asked Questions.md

@@ -23,28 +23,32 @@ The core functionality consists of three screens:
 
 ### Part 1
 
-The home screen should display a list of the questions that users have asked. This should include:
+The home screen should be visible without needing to log in should display a list of the questions that `users` have asked. This should include:
 
 1. The title
-2. The summary
-3. The status (has the question been answered)
+2. A short multi-line summary of no more than 250 characters.
+3. The username of the person asking the question.
+3. The status from the following:
+    1. unanswered (no-one has provided an answer).
+    2. answered (there is at least one answer provided).
+    3. solved (the person asking the question has flagged an answer as correct).
 
 ### Part 2
 
-There should be a button or link on the homepage that takes users to a screen where they can ask their own questions. They should supply:
+There should be a button or link on the homepage that takes `users` to a screen where they can ask their own questions. They should supply:
 
 1. A brief title
-2. A short multi-line summary
-3. A detailed, formatted, multi-line description of the question
-4. an optional image (screenshot or photo)
+2. A short multi-line summary of no more than 250 characters.
+3. A detailed, formatted, multi-line description of the question.
+4. an optional image (screenshot or photo) that should be uploaded from their computer.
 
 ### Part 3
 
-If the user clicks on one of the titles on the homepage they should be taken to the details page which includes the following features:
+If the `user` clicks on one of the titles on the homepage they should be taken to the details page which includes the following features:
 
 1. The title, summary and description of the problem
-2. A multiline input box to allow users to answer the question.
-3. If the logged-in user was the one who posted the question they should be able to flag one of the answers as correct.
+2. A multiline, formatted input box to allow `users` to answer the question.
+3. If the logged-in `user` was the one who posted the question they should be able to flag one of the answers as correct.
 
 ---
 

08 Gallery.md

@@ -3,25 +3,57 @@
 
 Build a website for up and coming artists/photographers to advertise their products.
 
+---
+
+## Testing
+
+The system should include at least five items for sale from each of the artist accounts listed below.
+
+You are required to create the following accounts to allow the system to be tested. All accounts should have the password `p455w0rd`:
+
+1. `artist1`
+2. `artist2`
+3. `buyer1`
+4. `buyer2`
+
+---
+
 ## Stage 1
 
-The core functionality consists of three screens:
-
-1. The home page should display all the items that all the artists want to sell arranged with the most recent at the top. Each should have:
-    1. The name of the item
-    2. A thumbnail image
-    3. The price the seller is asking for
-    4. A status (for sale, under offer, sold)
-    5. The name and phone number of the seller
-2. There should be a link on this page to the user's _selling_ page which should list all the items the logged-in user has for sale. This should include:
-    1. The name of the item
-    2. A thumbnail image
-    3. The status (see above) with the option for the user to change the status.
-    4. The option to delete items.
-3. There should be a link or button on this page to add new items to the list. This page should ask for:
-    1. The item name
-    2. A photo
-    3. A detailed, multi-line, formatted description.
+The core functionality consists of three screens.
+
+### Part 1
+
+The home page should be viewable without needing to be logged in and should display **all** the items that all the `artists` want to sell arranged with the most recent at the top. Each should have:
+
+1. The name of the item
+2. A thumbnail image
+3. The price the seller is asking for
+4. A status, one of the following:
+    1. for sale.
+    2. under offer.
+    3. sold.
+5. The name and phone number of the `artist`.
+
+### Part 2
+
+If a user is logged in, there should be a link on the home page that takes an `artist` page to their **selling** page which should list all the items they has for sale. This should include:
+
+1. The name of the item
+2. A thumbnail image
+3. The status (see above) with the option for the user to change the status.
+4. The option to delete items.
+
+### Part 3
+
+There should be a link or button on the **selling** page to add new items to the list. This page should ask for:
+
+1. The item name.
+2. A photo uploaded from the `artist's` computer.
+3. A detailed, multi-line, formatted description.
+4. The asking price.
+
+---
 
 ## Stage 2
 
@@ -36,6 +68,8 @@ The intermediate tasks require you to make changes to the functionality:
     5. Finally the seller should be sent a nicely formatted html email with details of the item and buyer plus a link to the item detail page
  public.
 
+---
+
 ## Stage 3
 
 1. Users should enter their paypal username when creating their account.

09 Game Reviews.md

@@ -3,25 +3,52 @@
 
 Build a community website to review games (you can choose what type). All the game details and reviews must be stored in a database.
 
+---
+
+## Testing
+
+The system should include the data for at least 5 valid games and each game must contain at least 3 sensible reviews posted from from valid user accounts (see below).
+
+You are required to create the following accounts to allow the system to be tested. All accounts should have the password `p455w0rd`:
+
+1. `user1`
+2. `user2`
+3. `user3`
+
+---
+
 ## Stage 1
 
 The core functionality consists of three screens:
 
-1. The home screen should include all the games that have been reviewed. For each there should be the following:
-    1. The name of the game
-    2. The publisher
-    3. The year of release
-    4. A thumbnail of the game box cover
-2. There should be a link on the home page to a page that allow users to add new games. This screen should ask for the following:
-    1. The game title
-    2. The publisher
-    3. The year of release
-    4. A full-sized image of the game box cover
-    5. A detailed, multi-line, formatted description.
-3. If a user clicks on the thumbnail or game title on the home screen they should be taken to the game review screen, this includes:
-    1. Details of the game (see section 2)
-    2. A list of the reviews given by the users with the most recent at the top and the oldest at the bottom. Each should include the name of the user, the date and the formatted text of their review.
-    3. A multiline input box to allow users to post their review. If a user has already reviewed the game the input box should not be displayed.
+### Part 1
+
+The home screen should be viewable without the need to log in. It should display all the games that have been reviewed. For each there should be the following:
+
+1. The name of the game.
+2. The publisher.
+3. The year of release.
+4. A thumbnail of the game box cover.
+
+### Part 2
+
+There should be a link on the home page to a page that allow logged-in `users` to add new games. This screen should ask for the following:
+
+1. The game title
+2. The publisher
+3. The year of release
+4. A full-sized image of the game box cover that has been uploaded from the `user's` computer.
+5. A detailed, multi-line, formatted description.
+
+### Part 3
+
+If a `user` clicks on the thumbnail or game title on the home screen, whether they are logged in or not, they should be taken to the game review screen, this includes:
+
+1. Details of the game (see section 2)
+2. A list of the reviews given by the users with the most recent at the top and the oldest at the bottom. Each should include the name of the `user`, the date and the formatted text of their review.
+3. If they are logged in they should also see a multiline input box to allow them to post their review. If a user has already reviewed the game or they are not logged in, the input box should not be displayed.
+
+---
 
 ## Stage 2
 
@@ -31,6 +58,8 @@ The intermediate tasks require you to make changes to the functionality:
 2. Each reviewed post should include the reviewer's first and last names as well as a profile picture (avatar) with a suitable default image used if this is not supplied. There will need to be a profile screen to allow users to update this information. Each user can only review each game once but they can edit their review.
 3. Users should be able to flag a review as being unsuitable or inappropriate. Once more then a specified number of users have flagged a review it should become hidden and the admin user should be sent an email with a link to the review and the choice of either deleting it or approving it.
 
+---
+
 ## Stage 3
 
 1. In addition, the site should be full-text searchable.

10 Gift List.md

@@ -3,23 +3,51 @@
 
 It is customary for events such as weddings for those tying the knot to make a list of the gifts they would like. Guests can then pick from the list to make sure they are buying something that is useful. All the gift list data and selections should be stored in a database.
 
+---
+
+## Testing
+
+The system should include the data for at least 5 valid events and each event should already have two items pledged from from valid user accounts (see below).
+
+You are required to create the following accounts to allow the system to be tested. All accounts should have the password `p455w0rd`:
+
+1. `user1`
+2. `user2`
+3. `user3`
+
+---
+
 ## Stage 1
 
 The core functionality consists of three screens:
 
-1. The home screen should display a summary of all the events that lists have been created for, including:
-    1. A brief title
-    2. A thumbnail image
-    3. The date of the event
-2. There should be a button or link on the homepage to allow users to create new events. The following information should be requested:
-    1. The event title
-    2. A full-size image to represent the event
-    3. The date when the event is taking place
-    4. A detailed, multi-line, formatted description of the event
-    5. Space to add up to five items to be added to the list, each to include the name, price and link to the online details
-3. Users should be able to click on one of the photos or event titles to be taken to an event screen which includes:
-    1. The details of the event (see previous point)
-    2. A list of the items wanted with each item showing its status (the name of the person who has pledged the item) or a link or button to allow the user to pledge.
+### Part 1
+
+The home screen should be viewable whether the `user` is logged in or not and should display a summary of all the events that lists have been created for, including:
+
+1. A brief title
+2. A thumbnail image
+3. The date of the event formatted as DD/MM/YYYY
+
+### Part 2
+
+If a `user` is logged in there should be a button or link on the homepage to allow them to create a new event. The following information should be requested:
+
+1. The event title
+2. A full-size image to represent the event uploaded from their computer.
+3. The date when the event is taking place selected from a date picker.
+4. A detailed, multi-line, formatted description of the event.
+5. Space to add up to five items to be added to the list, each to include the name, price and link to the online details.
+
+### Part 3
+
+Users should be able to click on one of the photos or event titles to be taken to an **event details** screen which includes:
+
+1. The details of the event (see previous point)
+2. A list of the items wanted with each item showing its status (the name of the person who has pledged the item).
+3. If the item has not yet been pledged, the `user` can click on a checkbox which assigns their name to pledge the item.
+
+---
 
 ## Stage 2
 
@@ -31,6 +59,8 @@ The intermediate tasks require you to make changes to the functionality:
     2. A link to the event screen
 3. When the original user receives the pledge (for example goods were delivered) they should be able to set the status of this on the system which should send out a personalised thank you email to the donor.
 
+---
+
 ## Stage 3
 
 1. Users should be able to send messages and questions to the person who created the list.

11 Local Community.md

@@ -3,40 +3,72 @@
 
 A local council wants to build a community hub to allow local residents to both raise issues and proactively help to solve them.
 
+---
+
+## Testing
+
+The system should include the data for at least 10 valid issues.
+
+You are required to create the following accounts to allow the system to be tested. All accounts should have the password `p455w0rd`:
+
+1. `user1`
+2. `user2`
+3. `council`
+
+---
+
 ## Stage 1
 
-The core functionality consists of three screens:
-
-1. The home screen should display all the issues that have been flagged by the users, this should include:
-    1. A brief title
-    2. The location of the issue
-    3. The status of the issue (new, verified, resolved)
-2. There should be a link or button on the home screen to allow a resident to add new issues, this should include:
-    1. The brief title
-    2. The location of the issue
-    3. A detailed, multi-line, formatted description.
-    4. An optional photo
-3. If a user selects one of the issues on the home screen they should be taken to am issues detail screen that should display:
-    1. The issue details (see last point)
-    2. An action link or button that allows a user to take charge of resolving the issue.
-    3. The original poster should also see a resolved link or button so they can confirm the issue has been resolved.
+The core functionality consists of three screens.
+
+### Part 1
+
+The home screen should be viewable whether a `user` is logged in or not and should display all the issues that have been flagged by all the `users`, this should include:
+
+1. A brief title
+2. The location of the issue
+3. The status of the issue, one of the following:
+    1. new
+    2. verified
+    3. resolved
+
+### Part 2
+
+if a `user` is logged in they should see a link or button on the home screen to allow them to add a new issue, this should include:
+
+1. The brief title.
+2. The location of the issue (provided as a valid postcode).
+3. A detailed, multi-line, formatted description.
+4. An optional photo uploaded from their computer.
+
+### Part 3
+
+If a logged-in `user` selects one of the issues on the home screen they should be taken to an **issues detail** screen that should display:
+
+1. The information provided by the `user` raising the issue (see last point)
+2. A **resolve** link or button that allows a user to take charge of resolving the issue and this should update the issue status displayed on the home screen. This link or button should not be visible to the `user` who raised the issue.
+3. If a `user` has clicked on the **resolve** link or button, the `user` who raised the issue should see a **resolved** link or button so they can confirm the issue has been resolved. This should update the issue status displayed on the home screen.
+
+---
 
 ## Stage 2
 
 The intermediate tasks require you to make changes to the functionality:
 
 1. A verify button that allows a user to verify that this is a valid issue (the button should be hidden from the user who initially posted the issue)
-2. The local council would like to use this app to allow them to prioritise the work the repair teams are scheduled to do:
-    1. There should be way for users to be identified as council workers to be able to log in and see a list of the jobs in order of distance from their current location.
-    2. Any jobs fixed by this team should be flagged as resolved by the council.
+2. The local `council` would like to use this app to allow them to prioritise the work the repair teams are scheduled to do:
+    1. There should be way for users to be identified as `council` workers to be able to log in and see a list of the jobs in order of distance from their current location.
+    2. Any jobs fixed by this team should be flagged as resolved by the `council`.
+
+---
 
 ## Stage 3
 
 1. Some of the users will engage with the system. To encourage this you will be implementing gamification elements:
-    1. Each time a user reports or verify an issue they get 10 points.
-    2. Each time an issue is resolved as fixed by the original reporter, the reporter gets 20 points and the person who fixed the issue gets 50 points.
-    3. The home page should display the top 10 users with the highest scorer at the top.
-2. Each time an issue is fixed, an email should be sent to the person who raised the issue, this should include:
+    1. Each time a `user` reports or verify an issue they get 10 points.
+    2. Each time an issue is resolved as fixed by the original `user`, they gets 20 points and the `user` who fixed the issue gets 50 points.
+    3. The home page should display the top 10 `users` with the highest scorer at the top.
+2. Each time an issue is fixed, an email should be sent to the `user` who raised the issue, this should include:
     1. The issue name, description and photo.
     2. A link to the details page.
     3. A button to click to resolve the issue.