Software Process

Process areas in Capabilty Maturity model describe the features of a products development. These process areas help to identify the level of maturity an organization has attained. These mainly include:

Project planning and monitoring

Risk Management

Requirements development

Process and Product quality assurance

Product integration

Requirement management

Product integration

Configuration management

Maturity level of a process defines the nature and maturity present in the organization. These levels help to understand and set a benchmark for the organization.

Five levels that are identified are:

Level 1: Adhoc or initial

Level 2: Repeatable

Level 3: Defined

Level4: managed

Level 5: Optimized.

A software process or software development process is a method or structure expected to be followed for the development of software. There are several tasks and activities that take place in this process. Different processes like waterfall and iterative exists. In these processes; tasks like analysis, coding, testing and maintenance play an important role.

Once the test is executed, a report of the results is displayed by WinRunner. The report shows all checkpoints, error and system messages that were encountered during execution. The test results window is used to account for any mismatches detected at checkpoints.

WinRunner has two types of recording modes:

1. Context Sensitive recording – records the operations that are preformed in an application by identifying the GUI objects.

2. Analog recording – records the inputs from keyboard, mouse clicks, the x and y coordinates that are travelled by the mouse pointer across the screen.

Quality Assurance (QA): QA refers to the planned and systematic way of monitoring the quality of process which is followed to produce a quality product. QA tracks the outcomes and adjusts the process to meet the expectation.

Quality Control (QC): Concern with the quality of the product. QC finds the defects and suggests improvements. The process set by QA is implemented by QC. The QC is the responsibility of the tester.

Software Testing: is the process of ensuring that product which is developed by the developer meets the user requirement. The motive to perform testing is to find the bugs and make sure that they get fixed.

Quality Assurance (QA): QA refers to the planned and systematic way of monitoring the quality of process which is followed to produce a quality product. QA tracks the outcomes and adjusts the process to meet the expectation.

Quality Control (QC): Concern with the quality of the product. QC finds the defects and suggests improvements. The process set by QA is implemented by QC. The QC is the responsibility of the tester.

Software Testing: is the process of ensuring that product which is developed by the developer meets the user requirement. The motive to perform testing is to find the bugs and make sure that they get fixed.

A good time to start the QA is from the beginning of the project startup. This will lead to plan the process which will make sure that product coming out meets the customer quality expectation. QA also plays a major role in the communication between teams. It gives time to step up the testing environment. The testing phase starts after the test plans are written, reviewed and approved.

The difference between smoke and sanity testing is described below:

Sanity testing is performed when new build is released after fixing bugs where as smoke testing is performed to check the major functionalities of the application.

Sanity is performed by the tester or the developer but smoke testing can be performed by the tester or developer.

Smoke testing is performed earlier where as sanity is performed after the smoke testing.

Sanity testing is narrow and deep approach of testing and smoke testing is focused testing based on major functionalities.

Destructive testing includes methods where material is broken down to evaluate the mechanical properties, such as strength, toughness and hardness.

For example, finding the quality of a weld is good enough to withstand extreme pressure and also to verify the properties of a material.

Benefits of Destructive Testing (DT)

Verifies properties of a material

Determines quality of welds

Helps you to reduce failures, accidents and costs

Ensures compliance with regulations

The testware is:

The subset of software which helps in performing the testing of application.

Testware are required to plan, design, and execute tests. It contains documents, scripts, inputs, expected results, set-up and additional software or utilities used in testing.

Testware is term given to combination of all utilities and application software that required for testing a software package.

Testware is special because it has:

1. Different purpose

2. Different metrics for quality and

3. Different users

Priority: concern with application from the business point of view.

It answers: How quickly we need to fix the bug? Or How soon the bug should get fixed?

Severity: concern with functionality of application. It deals with the impact of the bug on the application.

Ex.

High Priority and Low Severity:

Company logo is not properly displayed on their website.

High Priority and High Severity:

Suppose you are doing online shopping and filled payment information, but after submitting the form, you get a message like "Order has been cancelled."

Low Priority and High Severity:

If we have a typical scenario in which the application get crashed, but that scenario exists rarely.

Low Priority and Low Severity:

There is a mistake like "You have registered success" instead of successfully, success is written.

Software problem are listed below:

1. Purchasing the license of tool (QTP, selenium, QC, LR)

2. Lack of skilled Tester to run the tool

3. Expectation that automated tests will find a lot of new defects

4. Maintenance of automated tests

5. Technical problems of tools