Tag: testing

Scenario , Dry Run , Peer Group

Pre Meeting Preparations

Formal Follow Up Process

Includes Metrics

the use of a variable before it has been defined

unreachable (“dead”) code

memory leaks

array bound violations

requirements

documentation

test cases

improvements suggested by users

Security Testing

Recovery Testing

Performance Testing

Functionality Testing

Checking test logs against the exit criteria specified in test planning.

Logging the outcome of test execution.

Assessing if more tests are needed.

Writing a test summary report for stakeholders

Load Testing

Integration Testing

System Testing

Usability Testing

System Level Testing

Integration Level Testing

Unit Level Testing

Component Testing

The analysis of batch programs.

The reviewing of test plans.

The analysis of program code

The use of black box testing

Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.

Concurrently designing & testing the application.

Single user testing, determining the effects of accessing the same application.

Mainly concurrency testing refers to testing the application once it is fully designed.

Status reports are the elaborated results of testing cycle. These reports contain success of the product.

Status reports are the brief results of end to end testing cycle. These reports contain success of the product.

Status reports are the elaborated results of testing cycle. These reports contain success, warning and alerts of the product, just to ensure that there are no bugs in the product.

Status reports are the brief results of end to end testing cycle. These reports contain success, warning and alerts of the product, just to ensure that there are no show stoppers or blockers or hiccups in the product.