Software Testing Overview
Manual Testing Projects for Developing Nations
- Key Topics: Manual Testing & Types of Testing
- Different types of observations
- Various documents prepared during software testing
- Investment in project initiation
- Guide for new projects
- B.E. models (possible reference to project initiation models)
Software Testing Life Cycle (STLC)
- Starting Point: Requirement Analysis
- Importance of understanding PC software testing life cycle in detail
- Testing process and documentation:
- Observing the process of vesting roles for meditational projects
Project Introduction
- Development differences between project and product
- Projects: Specific customer requirements
- Products: Market requirements, used by multiple customers
- Advantages and applications
- E-commerce applications facilitated
- Different market product applications discussed
Functionalities of E-Commerce Applications
- Client journey:
- Login, search products, add to cart, check out, payment, and returns
- Functionalities include:
- User login and registration
- Modify account details
- Product search and filters
- Shopping cart and checkout processes
- Handling returns and customer feedback
- Frontend and Backend considerations
- User interface accessible to all internet users (frontend)
- Admin functionalities restricted to authorized personnel (backend)
- Internet & Intranet Applications
- Internet: Accessible to the public via the internet
- Intranet: Restricted access within an organization
Key Documents in Software Testing
- Documentation Importance:
- Requirement Specifications (RS)
- Functional Specifications (FS)
- Detailed documentation of functionalities (mock-up screens)
- How to prepare and validate documentation before initiation of testing
- Preparation and Testing Steps:
- Setting up initial environments
- Observing project keyword entries and exits
- Importance of documentation in understanding and executing testing processes
- How to handle deviations and report issues
Types of Testing
- Regression Testing: Re-testing after bugs have been resolved
- Exploratory Testing: Emphasizes discovery, investigation, and learning
- Automated Testing: Using automation tools
- Manual Testing: Hands-on testing by quality assurance personnel
- Beta Testing: Feedback from actual users
Risk Management & Mitigation
- Identifying potential risks
- Planning for resource allocation and backup strategies
Execution Strategies
- Test Plans & Cases Execution:
- Setting clear start and end points
- Specific steps for each testing phase
- Entry and exit criteria for different testing cycles
Tools and Reporting
- Use of specific tools for test management and documentation
- Reporting and tracking issues using bug tracking tools such as Bugzilla
- Maintenance of test environments and periodic updates
Summary
- Final Steps:
- Validate all documentation
- Review processes and gather feedback
- Continuous process improvement through repeated cycles of testing
Please subscribe to the channel for more updates!
Thank you!