DEV Community

Ragavi A
Ragavi A

Posted on

TASK 2

Q.NO:1 You are testing a form that allows users to schedule appointments with a doctor. The form has the following fields: first name, last name, email, phone number, and appointment date/time. Some more inputs:

If any field is blank, we should display "All fields are required"

  • If the email is invalid, we should display "Please enter a valid email"

If the phone number is invalid, we should display "Please enter a valid phone number"

  • If the appointment date/time is not available, it should display "Please choose another date/time"

  • If all fields are correct and the appointment is available, we should schedule the appointment successfully.

For these requirements write down the correct list of conditions in form of decision table

Condition Action
Any field is blank Display "All fields are required"
Email is invalid Display "Please enter a valid email"
Phone number is invalid Display"Please enter a valid
phone number"
Appointment date/time is Display "Please choose another
not available date/time"
All fields are correct and schedule the appointment
appointment is available successfully

Q.NO:2
Test Scenario 1: User Account Creation and Deletion
Test Steps:

  • Attempt to create a basic user account with valid credentials.
  • Attempt to create a premium user account with valid credentials.
  • Attempt to create an admin user account with valid credentials.
  • Attempt to create a user account with invalid credentials (e.g., weak password).
  • Delete a user account (basic, premium, and admin) successfully. Expected Results:
  • Basic, premium, and admin users should be able to create their accounts successfully with appropriate confirmation emails sent.
  • User accounts with weak passwords should not be created, and appropriate error messages should be displayed.

Test Scenario 2: App Navigation and Authorization
Test Steps:

  • Log in as a basic user and navigate through the app, attempting to access both limited and restricted features.
  • Log in as a premium user and navigate through the app, accessing all features.
  • Log in as an admin user and navigate through the app, accessing advanced settings and performing all actions.
  • Attempt to perform actions that require admin privileges with basic and premium user accounts. Expected Results:
  • Basic users should only be able to access limited features, premium users should access all features, and admin users should access advanced settings and perform all actions.
  • App should display appropriate error messages when basic and premium users attempt to access restricted actions.
  • App should not crash or face performance issues during navigation.

Test Scenario 3: Password Complexity and Confirmation Email
Test Steps:

  • Attempt to create user accounts with passwords not meeting complexity standards (e.g., too short, no special characters).
  • Verify that confirmation emails are sent upon successful account creation.
  • Check the content and formatting of confirmation emails. **Expected Results:
  • Users should not be able to create accounts with passwords that do not meet complexity standards, and appropriate error messages should be displayed.
  • Confirmation emails should be sent promptly upon successful account creation.
  • Confirmation emails should contain accurate information and be properly formatted.

Top comments (0)