Summary of "Manual Software Testing Training Part-1"
Overview
This is an introductory live training series on manual software testing aimed primarily at beginners. The instructor (live from Pune) covers both theory and practical, project-oriented exercises. Participants are encouraged to use chat for questions. Presentations and course materials will be shared during sessions.
Course structure (modules)
Module 1 — Fundamentals (theory)
- What is software and what is software testing
- Types and levels of testing
- Basic SDLC / STLC concepts and common process models (Waterfall, V‑Model, Spiral, Agile references)
- Basic testing terminology (bug / defect / failure / error) and software quality concepts
Module 2 — Practical project work
- Hands-on project (example: e‑commerce or other domain) to practice:
- Writing and documenting requirements
- Creating and executing test cases
- Reporting defects
- Testing of web and mobile applications:
- Test-case design and execution
- Receiving updates and reporting findings
- Interview preparation related to testing
Module 3 — Agile and tools
- Agile / Scrum basics (backlog, sprint planning, interaction with dev team)
- Introduction to JIRA (issue/requirement tracking) and other test-tracking approaches (Excel / documents)
Additional sessions
- Android app testing
- Differences between project-based and product-based development
- Quality parameters and deeper SDLC topics
- Future topics announced: SDLC, types of software/hardware, software quality metrics, Android testing, deeper bug/defect/failure distinctions
Key definitions and concepts taught
What is software?
Software is a collection of computer programs, typically grouped as:
- System software: operating systems and device drivers (Windows, Linux, macOS, Android)
- Programming software: compilers, interpreters, debuggers
- Application software: web apps, mobile apps, desktop apps (examples: Facebook, WhatsApp, Excel)
What is software testing?
Software testing is the activity within software development to detect and identify defects and ensure the product meets customer requirements. The main objective is to find defects and help deliver a quality product to the client/customer before release.
Bug / Defect / Failure / Error
- Human mistakes in requirements or code can create defects.
- A failure occurs when software does not behave according to expected behavior in the real (customer) environment.
- Testers identify deviations from expected behavior and report defects with reproduction details.
Quality parameters (what makes software “quality”)
- No critical bugs (ideally free of defects affecting functionality)
- On-time delivery
- Within budget
- Meets customer requirements and expectations (functional correctness)
- Maintainability (can be supported and fixed in production)
- Usability / user-friendly interface
- Reliability and consistency in the customer environment
Reasons defects occur
- Miscommunication or lack of clear communication between customer, business analysts, developers, and testers
- Complexity of the software and project (many modules, many developers)
- Changing or frequently updated requirements during development
- Developer errors or incomplete implementations
- Insufficient or inexperienced testing (skills gap in testers)
Practical skills, mindset and approach for testers
Start from basics
- Learn what software and software testing are
- Practice using common tools (MS Word, Excel, basic internet usage)
Step-by-step project-oriented approach
- Understand and document requirements clearly
- Create test cases linked to requirements
- Execute test cases and record actual vs expected results
- Log defects with reproduction steps, severity, priority (use JIRA or spreadsheets)
- Re-test fixes and perform regression testing when necessary
Tester mindset
- Think critically and try to “break” the application (negative testing)
- Be detail-oriented and reproduce issues consistently
- Communicate clearly with developers and stakeholders
- Keep learning (domain knowledge, tools, testing techniques)
Tools for tracking and communication
- JIRA for issue/requirement/test-status tracking
- Excel or documents for test case management (where required)
- Share test artifacts and presentations with the team/audience
Differences explained
Project vs Product
- Project: software built for a specific customer/requirement and used by that customer (custom solution)
- Product: software developed for a broad market and used by multiple customers (e.g., WhatsApp, MS Office)
Service companies vs Product companies
- Service companies typically deliver projects for specific clients (example: Infosys)
- Product companies build market software (examples: Google, Microsoft)
Session logistics and pedagogy
- Interactive learning emphasized (Q&A via chat), with practical exercises instead of dry theory
- Presentations and notes will be shared during/after sessions
- Trainer stressed importance of building practical skills before jumping into automation or advanced topics
Planned next topics
- Detailed SDLC
- Types of software and hardware
- Software quality attributes and measurement
- Android testing
- Clear distinctions between bugs, defects, and failures
Speakers / sources
- Main presenter / trainer (live from Pune) — primary speaker
- Names referenced (possibly participants or examples): Sohan, Shadi Singh, Awadhesh Singh, Sudhir Singh, Vinod, Vikas Yadav, Anil, Irfan Saifi, Laxman
- Tools/systems mentioned as sources: JIRA (issue tracking), Excel (test artifacts)
- Example products referenced: WhatsApp, Facebook, Amazon, Microsoft Office, Google services
Category
Educational
Share this summary
Is the summary off?
If you think the summary is inaccurate, you can reprocess it with the latest model.
Preparing reprocess...