Test Bed: Clean the Test machine and install required software.
Sanity Test: A sanity test is a narrow
regression test that focuses on one or a few areas of functionality. Sanity
testing is usually narrow and deep.
Smoke Test:- It
is a quick Test, doing after build deployment. Test the screens navigation and
data display.
In software industry smoke
testing is a shallow and wide approach whereby all areas of the application
without getting into too deep is tested
Module Test: Module is having a group of relating requirements .Test the
implemented requirements in the present module.
Integrating Testing: After Integrating Modules need to test dependencies between the
modules. Dependencies are like…….
Content
Data
Navigation
Integration
is a piece of code. Developers are responsible for Integration. Integration
testing responsibility is for testers.
Integration
Types:
Incremental Model
Classical Model
While Integrating they can follow bottom up or Top down approach.
Test Stub: It is a Dummy Program. It takes Input and returns the value. Return
value may be hard coded (Fixed value).They are not implementing only Business
code in this Program.
Test Driver: Create DLL (Dynamic Link Library) and
get the Return value.
Test stub and Test Drivers are developed by Developers.
In Bottom up approach use Test Driver & Test stub.
In top down approach use test stub only.
Difference between Incremental and Classical Model…………
In Incremental Model integrate one by one Module.
In classical Integrating Model integrate Modules according to our
requirement.
System Testing: Testing the End-to-End flow of the application.
Module Testing test case are designing with referring low level
design document. Test the field validation and UI.
For Integration test cases refer high level design document and
requirement.
System Test cases design with SRS and HLD & LLD.
Acceptance Testing:
In this Testing new Tester, Test Lead, Managers and Client are
involving.
As a Regular Tester we provide our support to them.
Acceptance Testing is 2 Types:
a) Alpha Testing.
b) Beta Testing.
Project: Which application is
developed for single client is called Project.
Product: Which application is
developed for multiple Clients is called Product.
Alpha Testing: It is called as In-house Test. This is mandatory for Product and
optional for Project. All high level Bugs which are found in this Testing those
are fixing.
Beta Testing: This is mandatory for Project as well as Product. This is doing at
Client place. Any showstopper Bugs found those is fixed. Remaining Bugs fixed
on later release or with service pack or patch.
Performance Testing: Testing the Application Performance under various working
conditions.
Under Performance Testing we are not testing all features. We cover
critical and frequently using functionalities.
Performance Testing Parameters:
1. Response time.
2. Execution time.
3. Server resources.
4. Network Performance.
5. Through put.
Response Time: The time from request to the time when first bit response started.
Execution Time: The time from request to the time when the request executed completely.
Through Put: The amount of work done for a unit time is called through put.
Example:
No. of Server hits for a minute, shows how many users uses the
application for a minute.
1. Identify the requirements.
2. Identify the functionalities.
3. Identify the scenario.
4. Develop the script.
5. Execute the Script and record the results.
6. Analyze the results .if not satisfied do the Performance queen and
continuously repeat 4th & 5th step up to satisfying
the results.
Volume Test: Testing the application
performance with different volume data. We are testing application performance
with high volume data as well as low volume data and make sure application
performance is uniform for all volume data.
If
any unexpected delay we absorve in the application below are the reasons for
delay.
Server resources.
Network performance (speed).
Poor design of application.
Execution: Performance Test we can execute manually or
programmatically or using tools. Simulation is little bit difficult manually
and programmatically.
Analysis:
Manually analysis is having limitations. Programmatically we can do.
With the help of tool we can do simulation and analysis without
issue.
Stress Test: Testing the application with a condition which is beyond the
requirement.
material, methods, qtp 10 vs qtp11, qtp testing, qtp script, script, system testing, test scenario, test plan, validation, UFT, verification, when,
ReplyDeletei have applied for upsc online application form here