SOFTWARE ENGINEERING SS 2024

Comprehensive Enterprise Resource Planning

(ERP) Software Solution

for Chambers and Associations

Task 4: Software Test & Refactor

Klaurent Madhi
Nikolai Maklakov
Abdul Rahman

Presentation Template from Canva Design Studio on Canva: Original Template Name: Technology in Education Technology Presentation in Blue Peach Illustrative Style
Agenda
KEY TOPICS DISCUSSED IN
THIS PRESENTATION

• Black-Box Testing
• White-Box Testing
• Project Reflection
• Conclusion
 Black-box Test Cases
Based on the documentation we have created these test cases :

Verifying that the registered companies list is displayed correctly

Observation : Failure (Instead the user can search for specific companies before logging in)
 Black-box Test Cases
Verify that a user can propose three company names for reservation

Observation : Pass
 Black-box Test Cases
Verifying that a registered member can log in to the member portal

Observation : Pass
 Black-box Test Cases
Verifying that a member can submit a query

Observation : Pass
 Black-box Test Cases
Verifying that a member can provide feedback on a resolved query

Observation : Failure (Member can write a feedback even if he hasn’t a resolved query )
 Black-box Test Cases
Verifying that an employee can manage member queries

Observation : Pass
 Black-box Test Cases
Verifying that the system prevents duplicate employee registrations

Observation : Failure (The duplicate employee is registered successfully)

 Black-box Test Cases
Verifying that members can update their profile information

Observation : Failure ( The use can’t update their profile information)

 Black-box Test Cases
Verifying that a member can successfully submit a review for an employee or service

Observation : Failure ( User can only submit general reviews not for specific query , user can submit even an empty review)
 Black-box Test Cases
Based on the documentation we have these test cases :

Verifying that the registered companies list is displayed correctly

Observation : Failure (Instead the user can search for specific companies before logging in)
White-Box Test Cases
These additional test cases were defined during inspection of the code. 26 in total with 9
failed :
White-Box Test Cases
Testing if empty comment is not written to CSV. AddMemberFeedbackTest Class
White-Box Test Cases
Testing if empty news is not added. AddNewsTest Class
White-Box Test Cases
Testing getters and setters of Company class. CompanyTest Class
White-Box Test Cases
Testing successful company registration on payment success
PaymentTest Class
White-Box Test Cases
Testing unsuccessful company registration with missing information
PaymentTest Class
White-Box Test Cases
Testing if invalid employee credentials are rejected. EmployeeLoginTest Class
White-Box Test Cases
Testing saving employee credentials with missing fields
RegisterEmployeeGUITest Class
 What went well? What didn’t go well?
• Found Critical Issues: We pinpointed key problems during • Unresolved Critical Issues: Some major issues are still
both black-box and white-box testing, covering both unresolved, posing risks to system functionality and user
functionality and code quality. This helps us focus on the experience. These need to be addressed promptly.
most important fixes. • Inconsistent Validation and Error Handling: Different
• Clear Recommendations Provided: For each issue, we parts of the system handle validation and errors
gave detailed recommendations, offering a clear path for inconsistently. This can lead to unpredictable behavior and
the next team to resolve these quickly. This proactive potential vulnerabilities.
approach helps ensure smoother transitions and faster • Limited System Integration: Integration between various
resolutions. system components wasn’t seamless. - Some
• Thorough Documentation: Every test case, whether it functionalities didn’t work together as intended, showing a
passed or failed, is well-documented. This gives future need for a more cohesive approach.
teams a valuable reference and ensures a shared
understanding of the system.
 What have we learned? What still puzzles us?
• Comprehensive Testing is Crucial: A well-rounded testing • Persistent Issues: Some issues remain unresolved despite
strategy, including both black-box and white-box testing, multiple testing phases. - This indicates there may be deeper,
is essential. This helps identify a wide range of issues, underlying problems.
from user interface problems to deeper code logic errors. • Unclear Integration Failures: Integration testing revealed
• Robust Error Handling and Validation: Effective error failures that aren’t easily explained. - The root causes of
handling and consistent validation are crucial for system these failures need further investigation.
stability and a good user experience. • Optimal Approach Uncertainty: There’s uncertainty about
• Effective Documentation is Key: Detailed and clear the best approach to resolve some of the more complex
documentation is essential for smooth project handovers. issues. - Additional research or consultation with experts
It supports continuity and makes it easier for new team may be needed to find effective solutions.
members to understand and continue the project.
Do you have any
questions?
Thank you for your time!