Welcome to the Guru99 Bank Demo Website Project repository! This project aims to create a fully functional and defect-free website for Guru99 Bank within a tight 13-day timeline. The primary goals include defect resolution, traceability, SRS verification, and thorough functionality testing.
- Project Overview
- Project Timeline and Milestones
- Getting Started
- Defect Resolution and Testing
- Contribution Guidelines
- Communication
- Contact
The Guru99 Bank Website Project is aimed at delivering a seamless user experience by addressing critical defects, ensuring traceability, verifying SRS compliance, and rigorously testing all functions of the website. By following these objectives, we intend to create a reliable and user-friendly website for Guru99 Bank.
-
Days 1-3: SRS Analyzing and Writing Test cases
- Clone the repository.
- Review the SRS document and identify initial Test cases.
-
Days 4-6: Execute Test cases and Bug tracking for V1
- Execute Test cases.
- Address defects through code changes and establish traceability.
-
Days 6-8: Execute Test cases and Bug tracking for V2
- Execute Test cases.
- Address defects through code changes and establish traceability.
-
Days 9-11: Execute Test cases and Bug tracking for V3
- Adding Test cases for new functions.
- Execute Test cases.
- Making system test plan
- Address defects through code changes and establish traceability.
-
Days 12-13: Documentation and Final Review
- Execute Test cases and Bug tracking for V4.
- Update project documentation, including this README.
- Review all project components and prepare for submission.
To contribute to the project, follow these steps:
- Clone the repository:
git clone https://github.com/Mochxd/Banking-Project-Guru99
- Review the Software Requirements Specification (SRS) document.
- Identify, resolve, and log defects.
- Identify defects and prioritize them based on criticality.
- Make code changes to address defects and maintain traceability.
- Create comprehensive test cases for all website functions.
- Execute test cases and document results in the traceability matrix.
- Verify alignment of functionalities with the SRS document.
- Fork the repository and create a new branch for your work.
- Make code changes and document them thoroughly.
- Submit a pull request, referencing related issues or defects.
- Your pull request will be reviewed before merging.
- Use [Gmail] for communication.
- For questions or assistance, contact [mohamedbadrxd@gmail.com].