Entries Tagged 'Manual Testing' ↓

How NOT to Write Test Cases (Tips for New and Experienced Testers)

Test case writing is one of the primary activities of the QA team. We spend most of our time writing, reviewing, executing or maintaining these. It is quite unfortunate that test cases are also the most error prone.

The differences in understanding, organization testing practices, lack of time etc. are some of the reasons why we often see test cases that leave a lot to be desired.

There are lot of articles on our site on this very topic, but today’s post will be about How NOT to write test cases – a few tips that will be instrumental in creating distinctive, quality and effective test cases.
Continue reading →

How to Test JAVA Applications – Tips with Sample Test Cases (Part 1)

In this tutorial, we will learn the components involved in a Java application and the various types of testing that need to be carried out to ensure a high quality, bug free application.

This is a three part series on testing JAVA applications.

------------

  1. In this article, we will learn the J2EE components and Manual testing approach for a J2EE application.
  2. In the second, we will review the Automated testing approach for testing J2EE applications, and
  3. In the third we will review a comprehensive list of tools that are available for testing J2EE applications.

Continue reading →

Why End to End Testing is Necessary and How to Perform It?

Nobody wants to be known for their mistakes and their negligence, and same is the case with the Testers. When the Testers are assigned any application to test, then from that moment, they take the responsibility and the application also acts as a platform to show their practical and technical testing knowledge.

So, to describe it technically, to ensure that testing is done completely, it is necessary to perform “End to End testing. Continue reading →




How to Make Manual Testing More Efficient Using HP Sprinter

Today in this era of Automation Testing, almost in every QA testing departments’ automation is the first preference. But there are few QA departments where 70-80% of testing is carried out manually. Indeed, there are cases where quality is completely determined manually as no automation is carried out there.

One of the crucial reasons of companies to continue with manual test is the inability of automation tools to cope with the changes that some application faces on regular basis. In certain cases, the only option left with QA is of manual testing. Continue reading →

Test Cases Vs Test Scenarios – Which is Better? (My Experience)

6 years ago, while working with a medium sized MNC, when I suggested to document test scenarios rather than wasting time on preparing full proof document called test cases, all the heads turned to me in annoyance. The look on the faces was clearly conveying that I made a big mistake by suggesting it. Although no one denied the idea but no one even accepted. Everyone felt that following the tradition, i.e. writing test case document, would be safer. I could not argue.

test cases vs test scenarios

After 4 years, the company received a testing project, where the only constraint was time and only expectation was full proof Continue reading →