Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added .DS_Store
Binary file not shown.
10 changes: 10 additions & 0 deletions Week1/realworld-testing-activities.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
| Shared testing activities | Unique testing activities for web | Unique testing activities for mobile (used chrome on iphone) |
| :-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :------------------------------------------------------------------------------------------------------------------: | :---------------------------------------------------------------------------------------------------------: |
| Testing all buttons and links and evaluating wether each one performs the expected action. | Test the responsiveness of the app by resizing the browser's window and using the Chrome DevTools responsivness tool | Testing responsiveness by setting different screen sizes, different actual devices, or different emulator |
| Test the sign in feature by entering random values and see how the app responses (missing the @ symbol , missing the .com part, entering incorrect credentials....etc) | | Test how the app looks in both the portrait and landscape modes |
| Test the sign up feature by entering random values and see how the app responses (short password, using the email address or the username as passwords, using easy to guess password...etc) | | What happens when there's an incoming call ? |
| Test the 'popular tag' feature by clicking on different tags in it and evaluating the output ' | | Test if common gestures in modern apps work (e.g. swipe right or left to move to the previous or next page) |
| Test the favorite button on each post while logged in and while logged out | | |
| Test the pagination feature | | |
| Test adding a new post (how does the app response when there in no title or no content or they are too short) | | |
| Test deleting a post (is there a confirmation message or not) | | |
17 changes: 17 additions & 0 deletions Week3/TEST-PLAN.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
<h3 style='text-align: center'>Test plan for sign in feature of Conduit web app</h3><br>

**Introduction**: This test plan is written for the Sign in feature of Conduit web app<br>

**Scope**: The functionality of the 'Sign in' feature <br>

**Assumptions**:

- There is at least one valid set of credintials to be used in performing the tests<br>
- There is no bugs in other parts of the app that would cause the tests to fail.

**Environment**:
macOS 10.15.7 / Google Chrome Version 87.0.4280.88 (Official Build) (x86_64)

**Tools**: Manual test

**People**: The tests will be written and executed by the Testing Team
28 changes: 28 additions & 0 deletions Week3/Test-Scenarios.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
**_Feature_**: Signing in

**Scenario**: Sign in with valid credentials
_Given_ the user is already at the sign in page
_When_ the user enters valid email address
_And_ the user enters the valid password
_And_ the user clicks on 'Sign in'
_Then_ the user should be redirected to 'Your Feed' page

**Scenario**: Sign in with empty credentials
_Given_ the user is already at the sign page
_When_ the user leaves the credentials fields empty
_And_ the user clicks on 'Sign in'
_Then_ the user should see an error message "email or password is invalid"

**Scenario**: Sign in with invalid credentials
_Given_ the user is already at the sign in page
_When_ the user enters invalid email address
_And_ the user enters valid password
_And_ the user clicks on 'Sign in'
_Then_ the user should see an error message "email or password is invalid"

**Scenario**: Sign in with incomplete email address
_Given_ the user is already at the sign in page
_When_ the user enters an incomplete email address i.e.: missing '@'
_And_ the user enters valid password
_And_ the user clicks on 'Sign in'
_Then_ the user should see a hint to type a complete address