Files
testexperiment/Project2/explanations.md
2024-12-06 23:20:58 +03:00

65 lines
3.6 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
Decision Table Testing Scenarios
Explanation:
The decision table enumerates various combinations of conditions (employee status, special authorization, auditor status, hour of day, and weekend) and shows the expected outcome. The conditions chosen are representative samples from the decision space.
### Decision Table Tests
| # | isEmployee | hasSpecialAuth | isAuditor | hourOfDay | isWeekend | Expected Result |
|---|------------|----------------|-----------|-----------|-----------|----------------|
| 1 | False | False | False | 9 | False | Deny (false) |
| 2 | True | False | False | 9 | False | Allow (true) |
| 3 | True | True | False | 8 | False | Allow (true) |
| 4 | True | False | False | 17 | False | Deny (false) |
| 5 | True | False | False | 9 | True | Deny (false) |
| 6 | False | False | True | 9 | True | Allow (true) |
| 7 | False | False | True | 8 | False | Deny (false) |
| 8 | True | True | False | 17 | True | Allow (true) |
---------------------------------------------
Equivalence Partitioning Scenarios
Explanation:
Here, input domains are divided into equivalence classes. We pick one representative test from each class to reduce the total number of tests while still ensuring coverage of all logical categories.
### Equivalence Partitioning Tests
| # | Conditions (Representative) | Expected Result |
|---|----------------------------------------------------------|-----------------|
| 1 | Not Employee, Not Auditor, Hour=10 (within 916), Weekday=false (not weekend) | Deny (false) |
| 2 | Employee, No Special Auth, Not Auditor, Hour=10 (within 916), Weekday=false | Allow (true) |
| 3 | Employee, Special Auth, Any Hour (e.g., 17), Weekend=true | Allow (true) |
| 4 | Auditor, Hour=16 (within 916), Weekend=true | Allow (true) |
| 5 | Auditor, Hour=8 (before 9), Weekday=false | Deny (false) |
Equivalence Classes Considered:
• Employee vs. Non-Employee
• Auditor vs. Non-Auditor
• Special Authorization vs. No Special Authorization
• Inside vs. Outside Working Hours (916)
• Weekend vs. Weekday
---------------------------------------------
Boundary Value Analysis Scenarios
Explanation:
Boundary values are chosen around the critical time limits. For this scenario, critical hours are 8 (just before 9), 9 (start of working hours), 16 (end of working hours), and 17 (just after 16).
### Boundary Value Analysis Tests
| # | Conditions (Focus on Hour Boundaries) | Expected Result |
|---|-----------------------------------------------------------------|-----------------|
| 1 | Employee, No Special Auth, Hour=8 (just before start), Weekday=false | Deny (false) |
| 2 | Employee, No Special Auth, Hour=9 (start), Weekday=false | Allow (true) |
| 3 | Employee, No Special Auth, Hour=16 (end), Weekday=false | Allow (true) |
| 4 | Employee, No Special Auth, Hour=17 (just after end), Weekday=false | Deny (false) |
| 5 | Auditor, Hour=8 (before start), Weekend or Weekday (e.g., false) | Deny (false) |
| 6 | Auditor, Hour=9 (start), Weekend=true | Allow (true) |
| 7 | Employee, Special Auth, Hour=8 (any boundary), Weekend=true | Allow (true) |
Boundary Values Considered:
• Hours: 8, 9, 16, 17
• Weekend vs. Weekday, Employee vs. Auditor, Special Auth variations