Performance Testing vs. Load Testing vs. Stress Testing

Performance Testing, Load Testing and Stress Testing many times confused a lot and sounds similar. But the main difference is the purpose of each type of testing. It has been described as below:

Performance Testing:  In performance testing, the goal is not to find a bug in the software product, but to eliminates the bottlenecks and establishes a baseline/benchmark for future regression testing. Various parameters which can be gather during performance testing as response time, lapse time, network latency, etc.

Introduction to Selenium

Selenium is an open source web automation tool which can be used for performing functional test execution. It’s been developed by SeleniumHQ. It can be used for various testing activities such as regression testing, unit testing, sanity testing etc. across various web browsers. Basically it comprises of three components:
  1. Selenium IDE (Integrated Development Environment)
  2. Selenium Server (formerly known as Selenium RC Server)
  3. Selenium Grid
It supports various scripting language such as Java, Python, Ruby, C#, etc for the automation. It can also run on various OS such as Windows, MAC and Linux. Latest version  of selenium can be download from their website: http://seleniumhq.org/download/

Alpha Testing vs Beta Testing

Alpha Testing: It is a type of testing performed at the development site. Sometimes it consider as testing which can be conducted at early and unstable stage of a software product.

Beta Testing: It is the type of testing which is performed at the customer site with an uncontrolled environment as in case of the alpha testing.

So in general the only difference between these two kinds of testing is the location where the application is being tested.

PDCA Cycle

PDCA cycle has got four important phase during the software development lifecycle. These are:
  • Plan
  • Do (or Execute)
  • Check
  • Act

Documents Available for Software Development


Project Initiation Note (PIN)
This document describes proposal and overall plan to develop a new software product.

Business Requirement Document (BRS)
This document consists of complete and correct requirements to develop the new software product.

Software Requirement Specification (SRS)
This document specifies how to develop the new software.

High Level Design (HLD)
This document specifies overall architecture of software in diagrammatic notation. This document is also known as “Architectural Design”.

Low Level Design (LLD)
This document describes internal logic of every module or functionality in a diagrammatic notation.

The process of verifying the correctness and completeness of PIN, BRS, SRS, HLD & LLD
Review Process

Evolution Of Coded UI

Microsoft Coded UI has been introduced with Visual Studio 2010. Initial day, when Visual Studio 2005 was available in the market and it comes as Test Edition. It can be used for the following testing related activities:

1. Unit Testing
2. Performance Testing
3. Web Test Automation
4. Manual Test

Comparing Visual Studio 2008 with 2005 there is no significance changes made in terms of testing features.
In Visual Studio 2010 Microsoft has introduced many functionalities as follows:

1. Microsoft Coded UI
2. Unit Test
3. Web Automation Test
4. Performance Test
5. Manual Test
6. Lab Management
7. MTM

Quality Assurance vs Quality Control

Quality Assurance (QA):
To release a quality software to customer an organization is monitoring and measuring the strength of its software development process. This check up is called as "Quality Assurance".

Quality Control (QC):
During software development an organization is validating each deliverables for correctness and completeness, This validation process is called as "Quality Control". In other word, quality control is consider as "Testing".