Test Case Design Techniques

Task 1 : Decision Table for appointment form

• The table tests a doctor's appointment form with fields: First Name, Last Name, Email, Phone Number, and Appointment Date.

• Each test case (TC01–TC09) checks different combinations of valid and invalid inputs.

• Expected results include:

  • ✅ Success when all fields are valid (TC01).

  • ❌ Error messages for:

    • Invalid email → “Please enter a valid email” (TC02)

    • Invalid phone number → “Please enter a valid phone number” (TC03)

    • Unavailable appointment date → “Please choose another date/time” (TC04)

    • Any missing field → “All fields are required” (TC05–TC09)

• This helps ensure the form responds correctly and guides users with clear messages.

Table:

Screenshot for your reference:

Testing a Mobile App – Test Case Overview

In this blog, I’ve highlighted key test cases for a new mobile app with Basic, Premium, and Admin users. Core features tested include role-based access, account actions, app performance, and permissions.

---

🔐 1. Role-Based Access
Verified access for each role:

• Basic: Limited features

• Premium: Full access

• Admin: Full + advanced controls

📝 2. Account Creation

• Created accounts with valid inputs

• Checked error handling for weak/invalid credentials

🗑️ 3. Account Deletion

• Ensured users can delete their accounts and get confirmation

🚀 4. App Stability

• Navigated through the app to check for smooth performance (no crashes)

⛔ 5. Unauthorized Actions

• Verified users get clear error messages when accessing restricted areas

---

📌 Conclusion:
These cases ensure the app works well, enforces access rules, and handles user actions reliably.

Screenshot for reference:

Table: