Tag: 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.

Testing each end of the application.

Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

Testing each module of the application and make sure each of them is working fine.

Testing each module of the application and making sure that none of them is having any bug.

If there is a discrepancy in code then the best approach is to check the use case documents for functionality. If the functionality is misunderstood by the tester then he will not raise a bug and to make things clear he can involve the project manager.

If there is a discrepancy in code then the best approach is to check the use case documents for bugs. If the functionality is misunderstood by the tester then he will not raise a bug and to make things clear he can involve the project manager.

If there is a discrepancy in code then the best approach is to check the requirement documents for functionality. If the functionality is misunderstood by the tester then he will not raise a bug and to make things clear he can involve the business analyst

If there is a discrepancy in code then the best approach is to check the requirement documents for functionality. If the functionality is misunderstood by the tester then he will not raise a bug and to make things clear he can involve the QA lead.

Running a system for a long period of time. For example,running the application for 2-3 days.If the application doesnt work properly then it is sent back to the devlopment team .

Soak testing refers to the testing of individual module of the application & making it error free.

Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of t

.Running a system at low load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of t

Testing the pre-recorded messages in the Interactive voice response systems.

Testing the messages in the Interactive voice response systems.

Testing the internel working of the Interactive voice response systems.

Testing the call routing/path of the Interactive voice response systems.

SPLATT

MAD

PL FILE

None of these

ML, RC,PS

ML, PS, Select

ML,RC,PS &SELECT

ML, RC, SELECT

SPLATT

MAD

PL FILE

None of these