effective bugs

Creating Effective Bugs

By – Shraddha Pande
A skilled QA tester knows that the most important part of the role is perhaps the ability to create effective bugs. A bug is not useful to the testing process if it is not reproducible and properly documented. Developers rely on clear and understandable bug reports to pinpoint what needs to be fixed.Thus, it is critical that these reports and the identified bugs capture all of the necessary data and criteria.


An effective bug must have these qualities:

    • Easily Reproducible:

The basic feature of a bug report is that it must be easily reproduced. For this it should have these:

  1. Title: The bug title should be a one-line accurate description.
  2. Steps: The steps to reproduce the bug must be few, clear and relevant.
  3. Summary: The actual and expected results must be descriptive enough so that the developer has a clear understanding of the problem. The expected results must describe precisely what needs to be fixed.
  4. Additional help: Whenever possible, attach a screenshot or video of the bug to the bug report to give the developers a more complete picture of the bug scenario.
  5. Platforms affected: Check the bug in all possible environments. For example, in website testing, one would run the scenario with different operating systems, browsers and mobile devices (versions and platforms) to reproduce the bug in different environments.
  • Severity and Priority:

The bug found should be labeled with the Severity (Critical, Major, Normal, Minor, Trivial and Enhancement) it can cause to the application as well as the Priority (High, Medium or Low) in which it has to be fixed.

  • Not a Duplicate:

The bug should be checked with the other bugs tracked to avoid duplication.

  • Deferrable or Not Deferrable:

Internal testers should also check the bug to ascertain if it can be fixed in the next build release.
After these steps are completed, the QA engineer checks all of the above features, discusses the bug found with the testing lead and development team and then, finally, creates the bug.


While the overall process outlined here is the basis of effective bug production, never underestimate the importance of good communication skills in the successful documentation and verbal explanations of the issues. A knowledgeable and respectful dialogue between QA and development leads to greater understanding of the issues and a stronger end product.
Visit us at www.thinksys.com , drop us an email at – buzz@thinksys.com for connecting with us.

manual testing procedure

Is Manual Testing Still very critical?

By – Shraddha Pande

The businesses imperative to drive value into the market at a faster and faster pace often translates into shorter development and delivery cycle times. And even with a top-notch development team, only a well-planned and systematic test plan will ensure that your products function as expected across Web and mobile channels when introduced to the marketplace.

A primer on manual testing of software

When selecting a particular testing approach, don’t ignore the most basic testing method of Manual Testing. Sometimes considered elementary, this testing technique is also the oldest and most stringent form of testing software products. It is done by a test engineer who behaves and works on the product or application as an end-user, executing the test cases manually without tool support. The test engineer verifies all the features of the application or product to ensure that the behavior of the application is correct and in accordance with the client requirements.

Adhering to the Software Testing Life Cycle, the engineer will create and follow a Test Plan to ensure the comprehensiveness of testing, while executing the test cases manually without using automation testing tools. The test engineer creates Test Cases to test the application via a certain set of steps that have defined Expected Results. These results are then checked against Actual Results. After executing these test cases manually, each functional test case is either marked as passed (with zero defects) or failed (having some defects). A benefit of manual testing is that all the test cases are executed manually executed by the testers, meaning that the program is less susceptible to machine faults.

Recommended Manual Test Process 

  1. Requirement Analysis: Determine and document the needs and requirements of the client, product, and application. Determine the needs and responsibilities for the testing process.
  2. Test Plan Creation: Build the Test Plan for the product/application on the basis of requirements developed in Step I. The Test Plan should include: Objective, Scope, Focus Areas, Time Estimation, Resources and Responsibilities.
  3. Test Case Creation: Create detailed Test Cases including Test Scenario.
  4. Test Case Execution: Execute the Test Cases to verify the actual and expected results.
  5. Defect Logging: Identified defects should be logged and tracked based on the conditions. We will discuss this more in our upcoming blog.“Creating Effective Bugs”.
  6. Defect Fix & Re-verification: After fixing any known defects, it is critical to re-verify and process them accordingly.

Recognizing the Value of Manual Testing in Today’s World

  • It delivers better usability testing than automated testing.
  • Greater assurance that the product or application is free from machine defects.
  • Delivers detailed program analysis.
  • This does a superior job at identifying non-testable requirements.
  • This type of can also provide better understanding of functionality.
  • Does a better job covering Test cases and Test Scenarios.
  • Manual testing scripts provide useful feedback to development teams and can form the basis for help or tutorial files for the application under test.
  • It can cover certain security aspects that automation tools are not designed to address.
  • It can lead to discovery of more complex vulnerabilities due to its flexibility. Humans can run a creative combination of attacks to discover any vulnerability out of reach of the automation test tools.
  • Automation testing benefits from building on the work already accomplished in the manual testing process.


In sum, it is important that QA teams recognize that Manual Testing can deliver critical results in the testing process. Manual Testing generally has lower up-front costs and allows a team to exercise flexibility during the testing process. Manual Testing can also be combined with an automated approach to deliver very positive and powerful results.

Keep looking at our blog section for more on this topic and click the link to know more about manual testing tools.

Visit us at www.thinksys.com , drop us an email at – buzz@thinksys.com for connecting with us.

test automation

Is Complete Test Automation Always Good?

With the advancements in technology and effective service delivery for businesses, QA and Testing service providers are venturing into automation. Automation may take the lead in accuracy but what about the flexibility, out of the box solution that a human resource can offer. Automation may be useful for tasks that are repetitive and do not require much human interaction thus focusing on the area it is designed for. But what the other related area and the bugs surrounding it that it may missed out.

As part of cost-effectiveness strategy, companies may think that all tests should be automated as it’s a one-time effort and provides cheaper solution rather than spend on many resources working manually. How true this thought is? Creating and maintaining automation tests do require resources along with the cost of the tools, hence the above thought may be true for some cases but not always.

Test automation is a great idea for projects where product is developed and needs to be strengthened. It may not be the right thing to do with new product testing. For a new product under test, a careful combination of manual and automated tests should be used so that testing activity does not overlook bugs that may be unforeseen by the automation. It may turn out to be costly in case bugs get overlooked by automation and are detected at a later stage. To make automation more effective, test cases for all the error scenarios have to be designed separately and this may be additional costly effort.
Automation of tests has its own side-effects as lots of bug may be missed in automation thus impacting the quality of the released product which may lower the customer satisfaction if they come up with those bugs.
In the end we can conclude that a careful combination of manual and automation testing may be a good approach as they alone may not prove as effective as it should be.