Advertisement

Computer Class Day 4 Level 3.pptx

Lecturer at Benson Idahosa University
Mar. 31, 2023
Advertisement

More Related Content

Advertisement

Computer Class Day 4 Level 3.pptx

  1. REQUIREMENT WHAT IS REQUIREMENT ? ⬜REQUIREMENT IS A DESCRIPTION OF HOW AN APPLICATION SHOULD FUNCTION ⬜REQUIREMENT DOCUMENT IS A DOCUMENT WITH A LIST OF REQUIREMENTS ⬜Also known as RSD (Requirement Specification Document), FSD (Functional Specification Document), REQUIREMENT
  2. SIMPLE REQUIREMENT • A USER SHOULD BE ABLE TO LOGIN TO THE APPLICATION USING THIS URL http://medical.mychurchmanager.com/
  3. USER STORY FORM ⬜ REQUIREMENT TYPE ⬜USER STORY ⬜EXAMPLE: ⬜AS A USER I WANT TO BE ABLE TO LOG IN TO MEDICAL APPLICATION PATIENT PORTAL SO THAT I CAN USE THE APPLICATION. Class Exercise GIVE EXAMPLES OF USER STORY AS A DAD, MUM, SISTER, STUDENT, ETC
  4. ACCEPTANCE CRITERIA SAMPLE ⬜ ACCEPTANCE CRITERIA GIVEN I AM A USER AND I AM ON MEDICAL APPLICATION PATIENT PORTAL WHEN I ENTER INVALID USERNAME ON USERNAME FIELD AND I ENTER INVALID PASSWORD IN PASSWORD FIELD AND I CLICK ON LOGIN BUTTON THEN THE SYSTEM SHOULD NOT LOG ME IN AND THE SYSTEM SHOULD GIVE ERROR MESSAGE INDICATING MY USERNAME AND OR PASSWORD IS INVALID
  5. LOGICS OF TESTING AN APPLICATION 1. POSITIVE TESTING 2. NEGATIVE TESTING 3. BLANK 4. BOUNDARY VALUE ANALYSIS 5. SPECIAL CHARACTERS
  6. BOUNDARY ACCEPTANCE CRITERIA • THIS IS BASED ON THE CHARACTER LIMITATION GIVEN FOR THE FIELDS. EXAMPLE – PASSWORD MUST BE BETWEEN 8 AND 20 CHARACTERS. • WHY CHARACTER LIMITATIONS? • GOOD SOFTWARE DEVELOPMENT PRACTICE • SECURITY AND SQL INJECTION ISSUE
  7. LOGIN USER STORY TO MEDICAL APPLICATION • LETS USE THIS A S A FORM OF PRACTICE • http://medical.mychurchmanager.com/
  8. USER STORY • AS A PARENT • I WANT TO BE ABLE TO LOG IN TO MEDICAL APPLICATION PATIENT PORTAL • SO THAT I CAN USE THE APPLICATION.
  9. COMMON LOGICS OF TESTING LOGIN USERNAME FIELD PASSWORD FIELD BLANK BLANK NEGATIVE TESTING BLANK VALID NEGATIVE TESTING BLANK INVALID NEGATIVE TESTING INVALID INVALID NEGATIVE TESTING INVALID VALID NEGATIVE TESTING INVALID BLANK NEGATIVE TESTING VALID INVALID NEGATIVE TESTING VALID BLANK NEGATIVE TESTING VALID VALID POSITIVE TESTING BOUNDARY BOUNDARY NEGATIVE TESTING/POSITIVE
  10. ACCEPTANCE CRITERIA FOR LOGIN USER STORY http://medical.mychurchmanager.com ACCEPTANCE CRITERIA 1 GIVEN USER IS ON PATIENT PORTAL URL WHEN USER LEAVES THE USERNAME FIELD BLANK AND USER LEAVES THE PASSWORD FIELD BLANK AND CLICKS ON LOGIN BUTTON THEN SYSTEM SHOULD NOT LOG USER IN
  11. ACCEPTANCE CRITERIA FOR LOGIN USER STORY ACCEPTANCE CRITERIA 2 GIVEN USER IS ON PATIENT PORTAL URL WHEN USER LEAVES THE USERNAME FIELD BLANK AND ENTERS VALID PASSWORD IN PASSWORD FIELD AND CLICKS ON LOGIN BUTTON THEN SYSTEM SHOULD NOT LOG USER IN
  12. ACCEPTANCE CRITERIA FOR LOGIN USER STORY ACCEPTANCE CRITERIA 3 GIVEN USER IS ON PATIENT PORTAL URL WHEN USER LEAVES THE USERNAME FIELD BLANK AND ENTERS INVALID PASSWORD IN PASSWORD FIELD AND CLICKS ON LOGIN BUTTON THEN SYSTEM SHOULD NOT LOG USER IN
  13. ACCEPTANCE CRITERIA FOR LOGIN USER STORY ACCEPTANCE CRITERIA 4 GIVEN USER IS ON PATIENT PORTAL URL WHEN USER ENTERS INVALID USERNAME AND ENTERS INVALID PASSWORD AND CLICKS ON LOGIN BUTTON THEN SYSTEM SHOULD NOT LOG USER IN
  14. ACCEPTANCE CRITERIA FOR LOGIN USER STORY ACCEPTANCE CRITERIA 5 GIVEN USER IS ON PATIENT PORTAL URL WHEN USER ENTERS INVALID USERNAME AND ENTERS VALID PASSWORD AND CLICKS ON LOGIN BUTTON THEN SYSTEM SHOULD NOT LOG USER IN
  15. ACCEPTANCE CRITERIA FOR LOGIN USER STORY ACCEPTANCE CRITERIA 6 GIVEN USER IS ON PATIENT PORTAL URL WHEN USER ENTERS INVALID USERNAME AND LEAVES THE PASSWORD FIELD BLANK AND CLICKS ON LOGIN BUTTON THEN SYSTEM SHOULD NOT LOG USER IN
  16. ACCEPTANCE CRITERIA FOR LOGIN USER STORY ACCEPTANCE CRITERIA 7 GIVEN USER IS ON PATIENT PORTAL URL WHEN USER ENTERS VALID USERNAME AND ENTERS INVALID VALUE IN THE PASSWORD FIELD AND CLICKS ON LOGIN BUTTON THEN SYSTEM SHOULD NOT LOG USER IN
  17. ACCEPTANCE CRITERIA FOR LOGIN USER STORY ACCEPTANCE CRITERIA 8 GIVEN USER IS ON PATIENT PORTAL URL WHEN USER ENTERS VALID USERNAME AND LEAVES THE PASSWORD FIELD BLANK AND CLICKS ON LOGIN BUTTON THEN SYSTEM SHOULD NOT LOG USER IN
  18. ACCEPTANCE CRITERIA FOR LOGIN USER STORY ACCEPTANCE CRITERIA 9 GIVEN USER IS ON PATIENT PORTAL URL WHEN USER ENTERS VALID USERNAME AND ENTERS VALID PASSWORD AND CLICKS ON LOGIN BUTTON THEN SYSTEM SHOULD LOG USER IN AND USER SHOULD SEE THE SELECT USER OVERLAY SCREEN
  19. DETERMINE HOW MANY TEST CASES • (2^3) +1 • (NUMBER OF FIELDS ^ NUMBER OF COMBINATION OPTIONS) + VALID CASE
  20. ASSIGNMENT • GO TO PATIENT PORTAL http://medical.mychurchmanager.com • COME UP WITH USER STORIES & ACCEPTANCE CRITERIA FOR: • (CHOOSE ONLY ONE PLEASE) • PROSPECTIVE CLIENTS OVERLAY • PATIENTS PORTAL SCREEN • RESET PASSWORD • REMEMBER ME
  21. WHAT IS TEST SCENARIO ? ACCEPTANCE CRITERIA 1 GIVEN USER IS ON PATIENT PORTAL URL WHEN USER LEAVES THE USERNAME FIELD BLANK AND USER LEAVES THE PASSWORD FIELD BLANK AND CLICKS ON LOGIN BUTTON THEN SYSTEM SHOULD NOT LOG USER IN TEST SCENARIO •VERIFY USER IS NOT ABLE TO LOGIN WHERE USERNAME AND PASSWORD FIELDS ARE LEFT BLANK.
  22. TEST SCENARIO ACCEPTANCE CRITERIA 2 GIVEN USER IS ON PATIENT PORTAL URL WHEN USER LEAVES THE USERNAME FIELD BLANK AND ENTERS VALID PASSWORD IN PASSWORD FIELD AND CLICKS ON LOGIN BUTTON THEN SYSTEM SHOULD NOT LOG USER IN TEST SCENARIO • VERIFY USER IS NOT ABLE TO LOGIN WHERE USERNAME IS BLANK AND PASSWORD IS VALID.
  23. TEST SCENARIO ACCEPTANCE CRITERIA 3 GIVEN USER IS ON PATIENT PORTAL URL WHEN USER LEAVES THE USERNAME FIELD BLANK AND ENTERS INVALID PASSWORD IN PASSWORD FIELD AND CLICKS ON LOGIN BUTTON THEN SYSTEM SHOULD NOT LOG USER IN TEST SCENARIO • VERIFY USER IS NOT ABLE TO LOGIN WHERE USERNAME IS BLANK AND PASSWORD IS INVALID.
  24. TEST SCENARIO ACCEPTANCE CRITERIA 4 GIVEN USER IS ON PATIENT PORTAL URL WHEN USER ENTERS INVALID USERNAME AND ENTERS INVALID PASSWORD AND CLICKS ON LOGIN BUTTON THEN SYSTEM SHOULD NOT LOG USER IN TEST SCENARIO • VERIFY USER IS NOT ABLE TO LOGIN WHERE USERNAME IS INVALID AND PASSWORD IS INVALID.
  25. TEST SCENARIO ACCEPTANCE CRITERIA 5 GIVEN USER IS ON PATIENT PORTAL URL WHEN USER ENTERS INVALID USERNAME AND ENTERS VALID PASSWORD AND CLICKS ON LOGIN BUTTON THEN SYSTEM SHOULD NOT LOG USER IN TEST SCENARIO • VERIFY USER IS NOT ABLE TO LOGIN WHERE USERNAME IS INVALID AND PASSWORD IS VALID.
  26. TEST SCENARIO ACCEPTANCE CRITERIA 6 GIVEN USER IS ON PATIENT PORTAL URL WHEN USER ENTERS INVALID USERNAME AND LEAVES THE PASSWORD FIELD BLANK AND CLICKS ON LOGIN BUTTON THEN SYSTEM SHOULD NOT LOG USER IN TEST SCENARIO • VERIFY USER IS NOT ABLE TO LOGIN WHERE USERNAME IS INVALID AND PASSWORD IS LEFT BLANK.
  27. TEST SCENARIO ACCEPTANCE CRITERIA 7 GIVEN USER IS ON PATIENT PORTAL URL WHEN USER ENTERS VALID USERNAME AND ENTERS INVALID VALUE IN THE PASSWORD FIELD AND CLICKS ON LOGIN BUTTON THEN SYSTEM SHOULD NOT LOG USER IN TEST SCENARIO • VERIFY USER IS NOT ABLE TO LOGIN WHERE USERNAME IS VALID AND PASSWORD IS INVALID.
  28. TEST SCENARIO ACCEPTANCE CRITERIA 8 GIVEN USER IS ON PATIENT PORTAL URL WHEN USER ENTERS VALID USERNAME AND LEAVES THE PASSWORD FIELD BLANK AND CLICKS ON LOGIN BUTTON THEN SYSTEM SHOULD NOT LOG USER IN TEST SCENARIO • VERIFY USER IS NOT ABLE TO LOGIN WHERE USERNAME IS VALID AND PASSWORD IS LEFT BLANK.
  29. TEST SCENARIO ACCEPTANCE CRITERIA 9 GIVEN USER IS ON PATIENT PORTAL URL WHEN USER ENTERS VALID USERNAME AND ENTERS VALID PASSWORD AND CLICKS ON LOGIN BUTTON THEN SYSTEM SHOULD LOG USER IN AND USER SHOULD SEE THE SELECT USER OVERLAY SCREEN TEST SCENARIO •VERIFY USER IS ABLE TO LOGIN WHERE USERNAME IS VALID AND PASSWORD IS VALID.
  30. TEST CASE DOCUMENTATION-1. VERIFY USER IS NOT ABLE TO LOGIN WHERE USERNAME AND PASSWORD FIELDS ARE LEFT BLANK STEP 1 STEP TAKEN/INPUT EXPECTED OUTCOME 1 Go to the url of AUT. Url as http://medical.mychurchmanager.com/pat ient/ Medical.mychurchmanager.com User should be on the Home page of Medical application. 2 Go to the Patient Login section. Leave the Username field blank. Leave the Password field blank. Click on Login button. System should display error message indicating username and password are mandatory.
  31. TEST CASE DOCUMENTATION- 2. VERIFY USER IS NOT ABLE TO LOGIN WHERE USERNAME IS BLANK AND PASSWORD IS VALID. STEP 1 STEP TAKEN/INPUT EXPECTED OUTCOME 1 Go to the url of AUT. Url as http://medical.mychurchmanager.com/pat ient/. Medical.mychurchmanager.com User should be on the Home page of Medical application. 2 Go to the Patient Login section. Leave the Username field blank. Enter INvalid value into Password field. Click on Login button. System should display error message indicating username and password are mandatory.
  32. TEST CASE DOCUMENTATION- 3. VERIFY USER IS NOT ABLE TO LOGIN WHERE USERNAME IS BLANK AND PASSWORD IS INVALID STEP 1 STEP TAKEN/INPUT EXPECTED OUTCOME 1 Go to the url of AUT. Url as http://medical.mychurchmanager.com/pat ient/ Medical.mychurchmanager.com User should be on the Home page of Medical application. 2 Go to the Patient Login section. Leave the Username field blank. Enter invalid value into Password field. Click on Login button. System should display error message indicating username and password are mandatory.
  33. TEST CASE DOCUMENTATION- 4. VERIFY USER IS NOT ABLE TO LOGIN WHERE USERNAME IS INVALID AND PASSWORD IS INVALID. STEP 1 STEP TAKEN/INPUT EXPECTED OUTCOME 1 Go to the url of AUT. Url as http://medical.mychurchmanager.com/patient/. Medical.mychurchmanager.com User should be on the Home page of Medical application. 2 Go to the Patient Login section. Enter invalid Username. Enter invalid Password. Click on Login button. System should display error message indicating username and password are mandatory.
  34. TEST CASE DOCUMENTATION- 5. VERIFY USER IS NOT ABLE TO LOGIN WHERE USERNAME IS INVALID AND PASSWORD IS VALID STEP 1 STEP TAKEN/INPUT EXPECTED OUTCOME 1 Go to the url of AUT. Url as http://medical.mychurchmanager.com/pat ient/. Medical.mychurchmanager.com User should be on the Home page of Medical application. 2 Go to the Patient Login section. Enter invalid Username. Enter valid Password. Click on Login button. System should display error message indicating username and password are mandatory.
  35. TEST CASE DOCUMENTATION- 6. VERIFY USER IS NOT ABLE TO LOGIN WHERE USERNAME IS INVALID AND PASSWORD IS LEFT BLANK. STEP 1 STEP TAKEN/INPUT EXPECTED OUTCOME 1 Go to the url of AUT. Url as http://medical.mychurchmanager.com/pat ient/ Medical.mychurchmanager.com User should be on the Home page of Medical application. 2 Go to the Patient Login section. Enter invalid Username. Leave the Password field blank. Click on Login button. System should display error message indicating username and password are mandatory.
  36. TEST CASE DOCUMENTATION- 7. VERIFY USER IS NOT ABLE TO LOGIN WHERE USERNAME IS VALID AND PASSWORD IS INVALID STEP 1 STEP TAKEN/INPUT EXPECTED OUTCOME 1 Go to the url of AUT. Url as http://medical.mychurchmanager.com/pat ient/ Medical.mychurchmanager.com User should be on the Home page of Medical application. 2 Go to the Patient Login section. Enter valid Username. Enter invalid value into the Password field. Click on Login button. System should display error message indicating username and password are mandatory.
  37. TEST CASE DOCUMENTATION- 8. VERIFY USER IS NOT ABLE TO LOGIN WHERE USERNAME IS VALID AND PASSWORD IS LEFT BLANK. STEP 1 STEP TAKEN/INPUT EXPECTED OUTCOME 1 Go to the url of AUT. Url as http://medical.mychurchmanager.com/pat ient/ Medical.mychurchmanager.com User should be on the Home page of Medical application. 2 Go to the Patient Login section. Enter valid Username. Leave the Password field blank. Click on Login button. System should display error message indicating username and password are mandatory.
  38. TEST CASE DOCUMENTATION- 9. VERIFY USER IS ABLE TO LOGIN WHERE USERNAME IS VALID AND PASSWORD IS VALID. STEP 1 STEP TAKEN/INPUT EXPECTED OUTCOME 1 Go to the url of AUT. Url as http://medical.mychurchmanager.com/pat ient/. Medical.mychurchmanager.com User should be on the Home page of Medical application. 2 Go to the Patient Login section. Enter valid Username. Enter valid Password. Click on Login button. System should log user in. User should see the Select Child overlay screen.
  39. PROCESS FROM REQUIREMENTS TO TEST CASES DOCUMENTATION EXAMPLE RELATIONSHIP FORMAT EPIC ACCESS TO APPLICATION FREE FORM FEATURE LOGIN FREE FORM USER STORY 1. VALID USER WITH RIGHT CREDENTIALS 2. VALID USER WITH INVALID CREDENTIALS 3. INVALID USER AS A …. I WANT TO…. SO THAT….. ACCEPTANCE CRITERIA WHAT SHOULD BE FULFILLED BEFORE USER CAN ACCEPT STORY GIVEN… WHEN…. THEN…. TEST SCENARIOS VERIFICATION OF EACH ACCEPTANCE CRITERIA VERIFY…….. TEST CASES STEPS TO VERIFY EACH ACCEPTANCE CRITERIA STEP TAKEN/EXPECTED/ACTUAL
  40. ASSIGNMENT 2 • WRITE THE FOLLOWING ON RESET PASSWORD FUNCTIONALITY ON MEDICAL APPLICATION • -EPIC • -FEATURE • -USER STORY • -ACCEPTANCE CRITERIA • -TEST SCENARIO • -TEST CASES
  41. INTERVIEW - BEHAVIORAL • Before your job interview – • be well informed about he company. • Tell me about yourself I really enjoy working as part of a team. In my last position as a QA Analyst, I worked on a number of team projects. One big project I was involved with at ACCENTURE was development of a new patient medical system for a client. It was a very challenging project as this was an NPI. Because of my past experience in Business Analysis I assisted the Business Analyst in requirement gathering. I also led the review of Test Cases written by my peers. At the end we were able to deliver a Quality application on time and Budget and our customers were very satisfied with us. I even got an award for the excellent work I did on the project.
  42. TELL ME ABOUT YOURSELF • POSITION • TEAM • PROJECT • WHAT YOU DID ON THE PROJECT • WHAT WAS THE END RESULT • YOU ARE HIGHLIGHTING SPECIFIC BENEFITS OF HIRING YOU
  43. DONTS OF INTEVIEW • DON’T BE TOO BRIEF • DON’T WEAR COLOGNE • DON’T BE LATE
Advertisement