Manual Testing Core Activities

Manual Testing Core Activities

What are the core activities of testing especially for manual testers? How should we plan testing efforts? Most of the time, I have seen effort of review activities and retesting of defects are being ignored heavily and schedule get hit because of that. Following are the core test activities should be considered while planning -


  • Test Ideas (Not Reviewed): Test idea is a test case with only summary and no details
  • Test Ideas (Reviewed L1): Test ideas reviewed by peer team member
  • Test Ideas (Reviewed L2): Test ideas reviewed by Test Lead / Test Manager
  • Test Ideas (Signed-off): Test ideas reviewed by client and signed-off
  • Test Cases (Not Reviewed): Test case is extension of test idea, putting more details around test idea (descriptive, detailed, Clear steps for execution, Test Data information etc.)
  • Test Cases (Reviewed L1): Test cases reviewed by peer team member
  • Test Cases (Reviewed L2): Test cases reviewed by test lead / test manager. Review of 100% test cases might not be possible.
  • Test Cases (Signed-off): Test cases reviewed by client. Review of 100% test cases might not be possible
  • Test Execution (Scripted): Exactly following the steps enumerated in the test cases. High chance of automating these test cases.
  • Update Test Cases (Execution): Update test cases during execution. It might be possible to find some missing or incorrect steps during execution
  • Test Execution (Exploratory): Session based exploratory testing
  • Defects Identified: Number of defects identified but not logged in defects tracking system yet
  • Defects Logged (Not Reviewed): Defects logged in defect tracker but not yet reviewed
  • Defects Logged (Reviewed): Logged defects are reviewed and updated
  • Defects Logged (Client): Defects are logged or shared to client for their review
  • Defects Retesting: Effort required for re-testing of fixed defects

Comments

Post a Comment

Popular posts from this blog

Performance Test Run Report Template

You have gathered requirements from clients, identified key critical business scenarios, analyzed the workload distributions, found out performance goals and requirements, identified  tool for generating load, setup the test environment, designed the scripts, executed the performance run, collected the raw data, analyzed it, what next?  Send information to stakeholders? No!!  Wait!! It needs to formatted, customized for different stakeholder(s) and reported accordingly. This article suggests one of the ways to report performance run results to client especially if the performance testing activity has been outsourced to yours company.  It discusses the performance report template and importantly the reasons for including the items in the report. The performance report template contains information by data collected from client side only and doesn’t discuss / talk about data from server side like processor utilization etc. Broadly the performance report has been divided in three major
Read more

Understanding Blockchain

This notes will cover below questions... Introduction to Blockchain What is the difference between Blockchain and Bitcoin? What are some other uses of blockchain that go beyond bitcoin? History of blockchain Could you explain the blockchain process in laymen terms? If all data is available to the public. Can anyone know my bank balance (in Bitcoin)? Introduction to Blockchain The Blockchain is a decentralized and distributed public (digital) ledger where transactions are recorded and confirmed anonymously. It’s a record of events that is shared between many parties. More importantly, once information is entered, it cannot be altered without altering subsequent blocks. WTF is the blockchain? A guide for total beginners What is the difference between Blockchain and Bitcoin? The blockchain is a technology
Read more

Bugs Management in Agile Project

Agile has a refreshing approach to bugs, especially when contrasted with traditional waterfall practices. Historically, teams would postpone bugs to a stabilization phase. This stabilization phase was long and tedious, typically with high stress and long hours. Agile, on the other hand, promotes the following thought processes: Carrying bug debt is unhealthy and sometimes, even destructive. We should fix bugs, not track them. A feature isn't done until the bugs are fixed. Quality is part of the overall cost. Bugs are prioritized against new features. A bug needs to be more important than the next new feature. Notes All new features have a "bug tail." The bug tail is the diminishing number of open bugs on the new functionality. When a feature is added, bugs are introduced. Most are discovered and fixed immediately by the team as a part of feature development: some a few days later, others not until long after a story is considered &quo
Read more