SDLC-Based System Testing & Requirements Validation Portfolio
| Category | Details |
|---|---|
| Project Type | Application Validation & Manual Functional Testing |
| Role Simulated | Technical Business Systems Analyst / QA Analyst |
| SDLC Phase | Testing & Validation |
| Application | SauceDemo Web Application |
| Testing Type | Functional & Negative Testing |
| Tools Used | TestRail, Excel, Postman (conceptual), Browser DevTools |
| Documentation | Test Plan, Test Cases, Defect Reports, Execution Evidence |
| Objective | Validate authentication workflows against expected requirements |
This repository demonstrates applied manual testing and system validation practices performed within a simulated enterprise Software Development Life Cycle (SDLC) environment.
The project focuses on validating authentication workflows of a web-based application through structured test planning, execution, defect management, and traceable documentation.
The work reflects responsibilities commonly performed by Technical Business Analysts and QA Analysts supporting application services, system implementation, and quality assurance initiatives.
User authentication is a critical entry point for enterprise systems. Failures in login functionality can lead to poor user experience, security risks, and operational disruption.
This project evaluates login workflows to ensure expected system behavior aligns with functional requirements and user interaction standards.
This portfolio project demonstrates practical experience aligned with responsibilities of a:
- Technical Business Systems Analyst
- Quality Assurance (QA) Analyst
- Information Systems Analyst
- Application Services Analyst
✔ Software Development Life Cycle (SDLC) participation
✔ Requirements validation and traceability
✔ Functional and negative testing design
✔ Defect lifecycle management
✔ Technical documentation and reporting
✔ System behavior analysis
✔ Quality assurance support for application releases
This project reflects how testing activities support enterprise system delivery by ensuring business requirements are validated prior to deployment.
This project simulates real-world Software Development Life Cycle (SDLC) testing activities by performing manual functional validation of the login functionality within the SauceDemo web application.
The objective was to evaluate system behavior across positive and negative user scenarios to ensure the application meets expected business and functional requirements related to authentication, usability, and input validation.
Acting in the role of a Manual Testing Analyst, this project demonstrates how testing supports business analysis by validating requirements, identifying defects, and producing traceable documentation that improves system quality prior to deployment.
- Functional validation of login workflows
- Positive and negative test scenario execution
- Requirement-based test case design
- Defect identification and documentation
- Evidence-based execution reporting
- 📄 Manual Test Cases (Excel)
- 🐞 Defect Tracking (Excel with supporting screenshots)
- 📸 Execution Evidence (timestamped screenshots)
- ✅ TestRail (test case management, execution tracking, and reporting)
Testing activities were aligned with expected acceptance criteria:
- Users must successfully authenticate using valid credentials.
- Invalid inputs must trigger appropriate validation messages.
- Locked users must be prevented from system access.
- Error messaging must remain consistent and user-friendly.
| SDLC Phase | Contribution |
|---|---|
| Requirements Understanding | Interpreted expected login behavior and acceptance criteria |
| Test Design | Created structured manual test cases |
| Test Execution | Performed functional validation |
| Defect Management | Documented and tracked defects with evidence |
| Validation | Confirmed expected system outcomes aligned with requirements |
This project covers the following login scenarios:
- Valid login for standard user
- Locked-out user validation
- Blank credential handling
- Incorrect credential validation
- Uppercase & special character inputs
- SQL injection attempt handling
- UI behavior and error message alignment
- Logout behavior and browser navigation handling
A total of 15 test cases were designed and executed.
Manual_Testing_SauceDemo_Login_Registration/
├── 1. SauceDemo_Test_Plan/
│ └── SauceDemo_Manual_TestPlan.docx
│
├── 2. SauceDemo_Test_Cases/
│ └── SauceDemo_Test_Cases.xlsx
│
├── 3. SauceDemo_Defect_Reports/
│ ├── SauceDemo_Defect_Report.xlsx
│ └── Defect_Screenshot/
│ ├── BUG001_TC005_error_msg_alignment.png
│ ├── BUG002_TC006_error_msg_alignment.png
│ └── ...
│
├── 4. SauceDemo_Test_Execution_Evidence/
│ └── Test_Case_Execution_Screenshots/
│ ├── TC005_Login_with_correct_credentials.png
│ └── ...
│
├── 5. SauceDemo_Test_Summary/
│ └── SauceDemo_Test_Summary_Report.docx
│
├── 6. SauceDemo_TestRail_Summary/
│ ├── TestRail_Run_Details.pdf
│ └── TestRail_Run_Outline.pdf
│
└── 7. README_SauceDemo_Manual_Testing.md
| Total Test Cases | Passed | Failed | Defects Logged |
|---|---|---|---|
| 15 | 15 | 0* | 7 minor UI issues (BUG001–BUG007) |
💡 *Some test cases revealed minor UI misalignments but were functionally successful.
- TestRail – Test management and execution tracking
- Microsoft Excel – Test case and defect documentation
- Microsoft Word – Test planning and summary reporting
- Browser DevTools – Validation and inspection
- Screenshot Tools – Evidence capture and reporting
- Software Development Life Cycle (SDLC) participation
- Manual Functional Testing
- Requirements Validation
- Test Case Design & Execution
- Defect Lifecycle Management
- Documentation & Traceability
- Business Workflow Analysis
- Quality Assurance Best Practices
Potential risks evaluated during testing included:
- Authentication failure scenarios
- Improper input validation
- UI inconsistency impacting usability
- Security-related input handling
Testing helped reduce risk by identifying UI alignment issues and validating expected system responses.
- Structured test documentation improves traceability.
- Early validation helps prevent downstream defects.
- Clear defect reporting accelerates issue resolution.
- Testing activities strengthen alignment between business expectations and system behavior.
This testing effort supports multiple stakeholders involved in application delivery:
- End Users: Ensures reliable and intuitive login experience.
- Business Teams: Confirms system behavior aligns with functional expectations.
- Developers: Provides clear defect documentation to support issue resolution.
- Quality Assurance Teams: Strengthens validation coverage prior to release.
- Organization: Reduces operational risk by identifying usability and validation issues early.
By validating authentication workflows, this project demonstrates how structured testing contributes to improved system reliability and user confidence.
This project demonstrates how structured testing activities support enterprise application quality by validating requirements, documenting defects, and ensuring reliable user authentication workflows prior to production deployment.
Tola Soyoye
Technical Business Systems Analyst | Manual QA Analyst
🔗 [LinkedIn] (https://www.linkedin.com/in/tola-s-484a0b22b/) 🔗 GitHub Portfolio: https://github.com/tollysho