> For the complete documentation index, see [llms.txt](https://wiredcraft.gitbook.io/recruitment-test/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiredcraft.gitbook.io/recruitment-test/qa/readme.md).

# README

For testing QA & QC positions. The tasks and results are sent with emails.

### Context

* We're building a WeChat Mini-program (MP) for a client
* The MP is a member-exclusive shopping center
* The client wants to attract users to purchase products through MP

### User-flows

1. All products have the same type, for example, shoes.
2. All products are visible to the guests, but once the user clicks "buy it", he/she must log in before proceeding.
3. Each product has multiple variations/measurements, such as colors and sizes, etc.
4. A product can become "sold-out", and that can be for a single variation (color/size/etc) or for the product as a whole.
5. The purchase flow starts with the user picking a variation (size/color/etc) and then clicking "buy it".
6. The user will then need to input the shipping address, email, etc.
7. Only after the user enters all the information, the system can calculate and tell the final price.
8. Then the user can move on to pay with WeChat Pay.

### Sample user story

* **US01**: As a User, I want to have a product list page (PLP) to browse all available products
* **US01.S01**: Display product list
  * WHEN user launch MP
  * AND goes to PLP
  * THEN the user can see all products, each with a product image and some basic information

### Tasks

#### 1: User stories

* Please analyze the requirements and describe what you think and what you would need to understand more (e.g., what questions you would ask the client) before the next steps.
* Please write user stories based on your understandings and assumptions for each of the flows, also make into consideration the MP native/common behaviors.

#### 2: Test cases

* Please list the acceptance criteria for the sample user story and all the stories you wrote.
* Please write at least 2 test cases for each of the stories - the sample and all of yours.

#### 3: Advanced requirements

*These are used for some further challenges. You can safely skip them if you are not asked to do any, but feel free to try out.*

* Imagine if we are planning to release the feature (the user-flow described above) within a month, can you provide a test schedule and scope plan (with some reasonable assumptions)?
* Imagine if you have finished the test plan and found some bugs, can you build a test report?

### FAQ

> Where should I send back the result when I'm done?

Put your answers in a PDF and email them back.

> What if I have a question?

Send us an email.