Fatma week3

Week1/HomeworkW1-RealWorld.md

@@ -0,0 +1,25 @@
+- **Shared testing activities** for web and mobile of *Real World App*:
+
+
+
+| Shared Testing; (Web & Mobile):  \**Testing Functionalities:\**( _of different buttons_:): | Behavior in Web |Behavior in mobile|
+| --- | --- | --- |
+|- The testing of `sign up` in both mobile & web: | This act as expected, the sign up created an account using web version. | This did not work in my mobile, the notification of verification of emails and passwords worked, but when it is come to the `Register` button, it does not work.|
+|- The testing of `New post` in both mobile & web: |This act as expected in web version as the empty fields were verified and the posts were created| This worked the same as in web.|
+|- The testing of `delete` & `edit` buttons in both mobile & web:|`delete` button worked as expected in web as the post was deleted.| `edit` button worked as expected when the content of the post was modified, but when empty the content and tried to save the edited posts, there was no notifications of importance of filled the fields of the post. The changes did not saved and the post saved with the previous contents instead.|Unlike in web version, both `delete` and `edit` buttons worked appropriately in my mobile.|
+|- The testing of `post` & `delete` *comments* buttons in both mobile & web:|`post comments` button worked as expected in web as the comments were posted, but `delete` comments button did not work.| Unlike in web version, both `post` and `delete` *comments* buttons worked appropriately in my mobile.|
+| - The testing of `follow` & `favorite` buttons in both mobile & web:  |-`favorite` button worked as expected in web, but `follow` button also worked when I follow my account.| `favorite` button worked as in the web, but `follow` button does not work when I follow my account, it just gave momentary change.|
+
+
+
+
+
+- **Unique testing activities** for web and mobile of *Real World App*:
+
+
+
+| Unique Testing (Web)| Unique Testing (Mobile)|
+| --- | --- |
+|- Testing buttons for `pagination` in the web. This feature worked as expected. | - While there was no tabs for pagination in mobile app, the test was perform on creating posts on using both 3G and wifi. The creating post feature worked appropriately in both network, but slower in 3G.|
+|- Testing the searching per `popular tags` worked also as expected | - The same, there was no buttons for `popular tags` in mobile version. So, I tested creating post while I was on 3G, at the moment of saving post, I changed to wifi. The post was not saved and did not even appear in the draft.|
+| |- `sharing` button worked appropriately in mobile app.

Week3/TestPlan.md

@@ -0,0 +1,121 @@
+**Test Plan for Khan Academy Website:**
+*Version 1,*
+*31/12/20*
+
+**1.1: Test Objectives:**
+* The system is easy to use
+* The functionality of the system components work perfectly
+* Identify possible defects in the system
+
+**1.2: Scope of Testing:**
+
+The testing for the Khan Academy Software system will include testing the following functionality:
+-	The searching functionality
+-	The login scenarios
+-	Change settings
+
+The testing will not be include: 
+-	The security of the system
+-	The donation component.
+-	Other functionalities which not mentioned in scoping.
+
+The testing environment will be desktops and different mobile application according to the high level of usage. The testing will use the most recent versions of Google Chrome, Internet Explorer and Firefox Browsers.
+
+**2: Approach:**
+**2.1 Assumptions/Constraints**
+**2.1.1 Assumptions** 
+-	The website is accessed in the mentioned browsers and machines
+-	The features of the websites, the prerequisites an behaviors of these features are well explained and understood by the team.
+-	The acceptance criteria are well stated and explained.
+**2.1.2 Constraints**
+- limitation of time
+
+**2.2 Coverage**
+ Test coverage will be measured by: 
+-	A completed matrix of testable requirements and test cases.
+-	A completed documents on features and their behaviors prepared in Gherkin to be easily automated for regression testing.
+
+**2.3 Test Tools**
+-	Manual testing using test scenarios and cases
+-	Automated testing using cucumber framework dependencies in node.js
+
+**2.4 Test Type:**
+Functional testing, by performing test cases based on testable requirements
+
+**3. TEST MANAGEMENT PROCESS:**
+
+**3.1 TEST MANAGEMENT PROCESS:**
+ ![Test Management Process](TestManagement1.PNG)
+**3.2 TEST EXECUTION PROCESS**
+  ![Test Execution Process](TestManagement2.PNG)
+
+**4. Plan:**
+
+**4.1: Required Resources**
+
+**4.1.1 Test Team:**
+
+|   **Title**  |   **Level of Involvement**   |  **Responsibilities**   |
+| --- | --- | --- |
+|Team Leader	| 40 hrs/wk	| Lead all testing activities, including test planning, test execution, and status reporting.|
+|3 Independent Testers	|40 hrs/wk	|Design and execute test cases. Automate test cases and scenarios for system testing|
+|Developers	| -	|To design and execute unit and integration testing|
+
+
+**4.1.2: Training of the team**
+
+**4.1.3: Hardware and other logistical requirements**
+
+
+**4.2 Team Reviews:**
+
+-	Test plan review 
+-	Test case review 
+-	Test progress review 
+-	Post-test review
+
+
+**4.3 Major Tasks and Deliverables**
+|**Task**|	**Start date**	|**End date**	|**Deliverables**| 
+| --- | --- | --- | --- |
+|Prepare test scenarios and test cases|	1/1/2021|	2/1/2021|	Initial test scenarios and test cases framework|
+|Review and approve test scenarios and test cases	| 2/1/2021	| 3/1/2021	| Approved test scenarios and test cases framework|
+| Train test team	| 4/1/2021	| 6/1/2021	| Trained testers|
+| Execute test scenarios and test cases	| 6/1/2021 |	9/1/2021 |	test summary and defects reports |
+| Automate test cases for re-testing and regression testing |	10/1/2021	 | 13/1/2021|	Automated framework|
+|Re-testing and regression testing	| 14/1/2021	|15/1/2021|	Final test report|
+
+
+
+** 5. Features to be Tested:**
+-	The searching functionality
+-	The login scenarios.
+-	Change settings.
+
+**(These features are only examples. I can see the gaps in the features to be tested against the time and resources. I can understand here that the features are much less compared by the time and resources and it is not realistic. This just an example of test plan for homework submission purpose)**
+
+
+
+**6. Features Not to be Tested**
+
+-	The donation component.
+-	Other functionalities which not mentioned in scoping.
+
+
+**7.  Defect Management:**
+
+The bugs or defects will be rated according to the priorities and risks as following:
+- Critical	Business objectives or completion of test case are impacted.
+- High	A certain functionality is not working as expected, for example, search button is not clickable
+- Medium	Defects which provide invalid/incorrect information.
+- Low	Defects related to esthetic of the website
+- Info	This type of priority could be assigned to a work order for an item encountered that is not clear in the requirements.
+
+
+**8. Risks and Contingencies**
+
+|**Risk**|**Probability**	|**Impact**|**Contingencies**|
+| --- | --- | --- | --- |
+|**SCHEDULE**   Testing schedule is tight. If the start of the testing is delayed due to design tasks, the test cannot be extended beyond the UAT scheduled start date.|	High	|High	|•	The testing team can control the preparation tasks (in advance) and the early communication with involved parties. •	Some buffer has been added to the schedule for contingencies, although not as much as best practices advise. 
+|**DEFECTS**   Defects are found at a late stage of the cycle or at a late cycle; defects discovered late are most likely be due to unclear specifications and are time consuming to resolve.  |Medium	|High|	Defect management plan is in place to ensure prompt communication and fixing of issues. 
+

Week3/TestScenariosAndCases.md

@@ -0,0 +1,79 @@
+**Test Cases for LogIn Scenario of Khan Academy Website**
+
+|Case ID| Test Case Description | Expected Results | Actual Result | Pass/Fail |
+| --- | --- | --- | --- | --- |
+|KHA_001| 	Check system behavior when valid email id and password is entered | Logged in | - | - |
+|KHA_002 | 	Check system behavior when invalid email id and valid password is entered. | User cannot log in: error message displayed | - | - |
+|KHA_003 | 	Check system behavior when valid email id and invalid password is entered. |  User cannot log in: error message displayed | - | - |
+|KHA_004 | 	Check Forgot your password is working as expected | The link is clickable showing change password form | - | - |
+
+
+** These test cases can be written in BDD using Gherkin as follows:**
+
+**Feature: User can log in to Khan Academy Website and start learning**
+
+
+**- Scenario: User enter correct login credentials**
+
+**Given** I visit "/login"
+
+
+When I enter "FatmaSalah@gmail.com" in the "user name" field
+
+
+And I enter "tester" in the "password" field
+
+
+And I press the "login" button
+
+Then I should be logged in Khan Academy.
+
+
+
+**- Scenario  User enter Incorrect login credentials**
+
+
+  **Given** I visit "/login"
+
+
+  When I enter "FatmaSalah11@gmail.com" in the "user name" field
+
+
+  And I enter "tester" in the "password" field
+
+
+  And I press the "login" button
+
+
+  Then I should not be logged in Khan Academy.
+
+
+**- Scenario User enter Incorrect login credentials**
+
+
+  **Given** I visit "/login"
+
+
+When I enter "FatmaSalah@gmail.com" in the "user name" field
+
+
+And I enter "tester111" in the "password" field
+
+
+
+And I press the "login" button
+
+
+Then I should not be logged in Khan Academy.
+
+
+**- Scenario User want to reset password to access Khan Academy**
+
+
+  **Given** I visit "/login"
+
+
+  When I click "forgot password" link
+
+
+  Then I should see the "change password" form.