Give short description on random software testing techniques?

Random testing is usually not followed because of its bad record as the case of worst program testing. But still it founds use in some of the software testing projects in the field. Though it has got a bad record, it is not always viewed as a foul case of software testing. 

What are in demand are the software testing methodologies that take in to consideration the structure of the software system or application that is to be tested. Path testing, partition testing etc were some of the resultant techniques that grew out of such demands. 

Is Random Testing Effective?

- After a rigorous research, simulation results were presented in which it was observed that it is not always that random testing is bad for testing, but sometimes it proves to be quite cost effective.

- Apart from the simulation results, the actual results of the random testing experiments were presented in which it was confirmed that the random testing is indeed a quite useful validation tool. 

- The random testing has been categorized under the black box testing techniques which involve the testing of the software system or application with an arbitrary sub set of all the possible input values. 

In this article we are going to discuss about the different techniques that can be used to carry out effective random testing. For random testing, the software testing strategies that take in to account the structure of the software system or application are usually preferred. 

Such two testing strategies are namely:

1. Path testing and
2. Partition testing

Random Software Testing Techniques

- Path testing is considered to be an instance of the partition testing and is hence usually deployed for the structural testing. 

- On the other hand, the partition test is usually used for random testing that works with any testing scheme which involves the forced execution of few test cases from the sub sets of a partitions of a domain from where input is supplied. 

- Simulation results as well as the results of actual random testing were presented and it was concluded from them that the random testing is quite an effective and need not always be a bad case.

- The actual random testing experiments results declared the random testing as a viable tool for validation testing. 

- Another technique for random testing is the simple black box random input testing.

- It is considered to be a crude technique that effectively locates most of the bugs in real time software systems and applications. 

- In this technique the software system or application is subjected to two kinds of input: With these simple parameters any application can be subjected to random testing. 

1. Streams of valid mouse and key board events
2. Streams of valid Win32 messages.

Goals of Random Testing Techniques

- Using the random testing techniques the command line applications could be crashed or hung. - The basic goal of any random testing technique is to stress the software system or application program. 

- In random testing you are required to simulate the user input in the testing environment.

- Firstly, the random user input is delivered to the software system or applications by putting this random input into the main communication stream between the server and the application. 

- In the case of first type of input data, complete random data was sent to the software systems since it provides an insight in to the level of robustness and testing of the software system. 

- Any failure can be encountered during the normal use of the software system. 

What role does documentation plays in development process?

Documentation is a set of documents or informational products to describe a computer system. Each document is designed to represent particular function like reference, instructional and motivational.
Some types of documentation and informational products are system features and functions, user and management summaries, users manual, video and multimedia, tutorials, demonstrations, reference guide, technical references, system test models,
operations/operators manual, wall charts, newsletters.

A useful document furthers the understanding of the system's desired andactual behavior and structure. The criteria for measuring usability of documents are readability, availability, suitability and accessibility.

Purpose of Documentation

- It provides a reasonably permanent statement of a system's structure or behavior through reference manuals, user guides and systems architecture documents.
- It serves as transitory documents that are part of the infrastructure involved in running real projects.

Importance of Documents and Manuals

- Cost saving.
- They serve as sales and marketing tools.
- They serve as tangible deliverables.
- They serve as contractual obligations.
- They serve as security blankets.
- They serve as testing and implementation aids.
- They are used to compare the old and new systems.

Overview of Regression Testing and its objectives.

Regression testing is an important part of the software development life cycle. regression means going back. If any kind of modification is done in software, testing needs to be done to ensure that it works as specified and that it has not negatively impacted any functionality that it offered previously.
Common methods of regression testing include re-running previously run tests and checking whether previously fixed faults have re-emerged.

The objectives of regression testing are :
- To identify uncovered and unexpected defects.
- To ensure that changes or additions in the code are safe & are not liable to break the existing functionality of the application.
- To ensure and track the quality of its output.
- The changes to the software application have not introduced any new bugs.

Regression testing is necessary when there is a change made to an existing tested software. Each change implies more regression testing needs to be done to ensure that the system meets the project goals.
Regression testing can become cost effective if the test cases are automated the test cases may be executed using scripts after each change is introduced in the system. Also, teams do not execute all the test cases during the regression testing. They test only what they decide is relevant.

In short, regression testing means rerunning tests of things that used to work to make sure that a change didn't break something else. The set of tests used is called the Regression Test Set. It's enormously helpful when you change an application, change the environment, and during integration of pieces.
Regression testing is a simple concept, but it needs to be done just right to work in the real world.