When we find out the bug, we will put into the “open” status. After fixing the bug developer change the status as “fixed”. Again we will test the fixed part, if there is no bug, change the bug status as “Closed” other wise change the bug status as “Reopen”.

Learn more »

The first scenario to be tested is the GUI. The page layout and the design elements used on the website have to be uniform throughout the website. The next part to be tested are the different links provided inside the website. Along with the links, it will also have to be tested, whether internal navigation is smooth and also check if it is complex. The next important aspect to be checked, is the response time of the website. This will also have to checked, when there is heavy load on the system.

Learn more »

The test case formats will vary depending on whether the website is a static website or a dynamic website. The static website will have the front end test cases, navigation test cases. On the other hand, if the website is a dynamic website, then the test cases will be broadly divided under front end test cases, back end test cases, field validations test cases, database test cases, security test cases, etc.

Learn more »

Some of the HTTP Response Objects are write, flush, tell, etc. The subclasses of HTTP Response are HttpResponseRedirect, HttpResponsePermanentRedirect, HttpResponseBadRequest, HttpResponseNotFound, etc

Learn more »

The most important factor that needs consideration is the hardware platform, while some may use the Mac platform, some may use Linux, while others may use Microsoft platform. The next comes the browsers and their versions into the picture. Along with the browser versions, the different Plug-Ins also have to be taken into consideration. The resolution of the monitor also with color depth and text size are some of the other configurations.

Learn more »

The browsers that are commonly used are Mozilla Firefox, Google Chrome, Internet Explorer and Opera. Therefore, a web application must be tested on these browsers as well.

Learn more »

Automation is the integration of testing tools into the test environment in such a manner that the test execution, logging, and comparison of results are done with little human intervention. A testing tool is a software application which helps automate the testing process. But the testing tool is not the complete answer for automation. One of the huge mistakes done in testing automation is automating the wrong things during development. Many testers learn the hard way that everything cannot be automated. The best components to automate are repetitive tasks. So some companies first start with manual testing and then see which tests are the most repetitive ones and only those are then automated.

Learn more »