I once collected some projects for testing practice; see the list in (), but most of these projects are still aimed at automation testing practice, and there are very few projects truly used to practice software testing and defect-discovery skills, so the idea of making such a project myself was born.
Design Approach
Taking the development of a project with real requirements as an example, it follows a simulated agile development process and iterates by Sprint. Each iteration is implemented according to the specified requirements, but at the same time contains some injected, known Bugs.
Practitioners can treat the branch corresponding to each iteration (such as sprint0, sprint1) as a version submitted for testing, and conduct testing and practice on it. At the same time, they can also
Invitation to Build Together
Individual strength is limited, so I now invite all fellow testers to jointly improve this Demo project, including completing test cases, supplementing the list of existing Bugs and other related documents, so as to strive to provide testing beginners with a Demo that closely reflects real software development and has real learning value.
Reply with join the group to enter the testing discussion group, exchange testing techniques with fellow testers, and improve and progress together~
Project Address and Introduction
https://github.com/chengxiaqiucao/TestMyBookshelf
sprint homepage

sprint1 homepage

Feel free to open more Issues~~
The ReadMe document is as follows:
Personal Book Management – My Bookshelf
A testing practice project | A library management system with injected defects | Implemented with FastAPI + SQLite | Suitable for QA training
This is a personal book management system used for testing practice. The project deliberately injects some typical Bugs for testers to practice Bug discovery and verification.
Project Features
Complete basic functions: implements basic functions such as adding, deleting, modifying, and querying books
Typical Bug injection: contains multiple common problem scenarios
Simple tech stack: uses a mainstream but lightweight technology combination
Suitable for testing practice: diverse Bug types with clear reproduction steps
Usage
Switch to different sprint branches and test against the requirements of each branch
Notes
This project is mainly for testing practice and is not recommended for production environments
All Bugs are deliberately injected for testing practice
Bug locations are not marked in the project code; testers need to discover them on their own
Testing Objectives
Verify whether all injected Bugs can be reproduced
Practice writing Bug reports
Become familiar with common Web application problems
Improve test case design skills
