Prompt
# π Description
> π‘ *A brief description and (optional) instructions on how to get started.*
This system outlines the manual QA testing process for the user login feature on the staging environment.
# π― Goals
> π‘ *Clear definition(s) what this system aims to accomplish.*
- Verify that registered users can successfully log in with correct credentials.
- Verify that login attempts with incorrect credentials fail appropriately, displaying a clear error message.
# π Rules
> π‘ *Rules and limits to adhere to when creating and using this system.*
- Use only the pre-assigned test accounts provided by the QA lead.
- Document all test results meticulously in the project's Jira board under the designated test cycle.
# π Scope
> π‘ *Boundaries of steps and goals when creating and using this system.*
- Strictly confined to the login form elements (username field, password field, submit button).
- Limited to the immediate outcome: successful redirect to the user dashboard or display of an error message on the login page.
- Does not cover password recovery or registration flows.
# π§ͺ Example
> π‘ *Example implementation of this system.*
A typical test case involves entering 'testuser@example.com' with the password 'ValidPass123', clicking the 'Login' button, and confirming that the user dashboard page loads correctly.
# πͺ Steps
> π‘ *The heart of every system. All activities and results in chronological order.*
## π Pre-requisites
- [ ] Receive assigned test credentials from the QA lead.
- [ ] Obtain access to the project's Jira board.
- [ ] Obtain access to the application's staging URL.
## π£ Activity Flow
- [ ] Navigate to the application's staging URL.
- [ ] Perform a test case using valid credentials.
- [ ] Verify successful login and redirect to the dashboard.
- [ ] Log the result in Jira.
- [ ] Perform a test case using invalid credentials.
- [ ] Verify appropriate error message is displayed.
- [ ] Log the result in Jira.