Embed Size (px)
Citation preview
7/28/2019 Knol 1
http://slidepdf.com/reader/full/knol-1 1/11
Home | Help | Sign in
Search Toolkit Search
Software Testing Theory Index
Software Testing Complete Theory
Environments
Software testing life cycle
Bug life cycle
ISTQB Chapters
ISTQB Tests & Answers
References
Save your Eyes : Green Search Engine: Testers approved
Let me start with a short Intro, I am a Self employed Musician and web developer, and have spent lot
of time understanding the software testing field and the stages of evolution in it. And I bring in front of
yo u a very ef fect ive smal l dose of test in g theory . (Thanks to Mr Suresh Reddy, My senior mentor at
NR ST T Hy de ra ba d fo r al th e gu id an ce an d co ac hi ng . ) I have divided the Concise Testing Theory
( C.T.T ) into the following sections.
Sections
W hat is Software Testing ?
W ho can do it? & Terminology.
Software Development Life
Cycle ( SDLC.)
T esting methodology & Levels
of testing.T ypes of Test ing.
Software Testing life cycle
Bug life cycle (BLC.)
A utomation Testing.
Performance Testing.
ISTQB & Software Certification
Each section is explained in Detail and will be enhanced as and when needed. Good luck and enjoy the
syllabi. I will shortly create concise knols on Sql server & QTP.
I do Believe Strongly that A good understanding of CTT can get you a job in IT ( at least in India, US, UK
& AU) very soon. All you need minimum is to be A graduate from any field ( 15 years of formal
education).
Software Testing?
Testing in general, is a process carried out by individuals or groups across all domains, where
requirements exist.
Whereas, In mo re softw are subject ive languag e, T he comparison of E V (expected value ) and
A V (Actual value) is known as testing.
To get a better understanding of the sentence above , lets see a small example,
Validat ion & Veri fica tion of any task can be call ed as Testi ng (1)
Contents
Software Testing Theory Index
¡ Software Testing?
¡ Who can do testing & things to understand ( Pre requirement to understand Software testing effectively)
¡ Software Development Life Cycle (SDLC)
¡ Software Testing Methods & Levels of Testing.
¡ Types of Testing:
¡ Sub Index :
Software TestingSoftware testing, Theory, ISTQB, Interview based theory, Manual & Automation Test
process, QTP, Loadrunner, Quality center, Software testing life cycle and terminology
Software testing - Complete Theory. A very detailed study & use of Software Testing from 199Os to
2008 has been digested about by several Major software companies and is evident in modern testing
metho dolog y. The following C T T (Concise testing thory) course should be of sufficient help to clear an
I.T. interview for software testing engineers, QA, Automation and Manual Test management team and
Performance testers alike.From manual to QTP, Load runner & Test management, the ever evolving testing field is drawing more
and more attention lately. Its a very high paying field in IT and has lot of opportunity. Lets discuss
everything that makes Software testing such an interesting topic.
lessmore
Link Citation Email Print Listen mp3 Favorite Collect this page
Edit this knol Write a knol
Vinayak RaoMusician, Software
tester, Googler at
officialiwant.com
India
Article rating:
Your rating:
0 Ratings
No rating
Creative Commons Attribution
3.0 License
Top Viewed Knol Award
Top Pick Knol Award
Version: 93 VersionsLast edited: Mar 14, 2009 3:20
AM.
Moderated collaboration
Be the first to review this knol
Vinayak Rao also wroteMicrosoft CRM
Software Testing Life Cycle
Mumbai need to strike back :
26/11 terror attacks
How to make Software testing
as easy as ABC - Entry to Knol
for Dummies ContestISTQB Certification, Answers of
All tests Chapter 1-6
(18 knols and collections)
Related KnolsWeb Software Testin...
by Ed Seward
Software Testing
by Akber Choudhry
Testing Fundamentals
by Saravanan Thiruna...
Software testing
by d venkata suresh
Program Testing
by Beya Adamu
Knol translationsHelp translate this knol into your
language.
Search for uses of this page ▼
Reviews
Categories
Automation testing, Internet, ISTQB,
reference, science, software
Sign in to add or vote for categories
Based on community consensus.
Learn more about categories
Activity for this knol
7/28/2019 Knol 1
http://slidepdf.com/reader/full/knol-1 2/11
Public activity feed
Flag inappropriate content
example 1.
I have a bulb , and my requirement is that when i switch it on, it should glow. So My next step is to
identify three things
Acti on to be perf orme d : turn the Swit ch on,
Expected value : Bulb should glow,
Actual value : P resent Status of the bulb after perform ing the action ,( on or o ff ) .
Now its the time for our test to generate a result based on a simple logic,
IF EV = AV then the result is PASS , else Any deviation will make the result as FAIL.
Now , ideally based on the difference or margin of difference between the EV and AV , The Severity of
the defect is decided and is subjected for further rectifications.
Conclusive Definition of Testing :
Testing can be defined as the process in which the defects are Identified, Isolated and then
subjected for rectification and Re ensuring that the end result is defect free (highest quality) in order toachieve maximum customer satisfaction. ( An Interview definition. ).
Who can do testing & things to understand ( Pre requirement to understandSoftware testing effectively)
As we have unde rsto od so far, tha t test ing is a very gen eral task and can be perf orme d by any bod y.
But we have to understand the importance of software testing first,
In the earlier days of software development, the support for developing the programs was very little.
Commercially very few rich companies used advanced software solutions.
As thr ee decades of res ear ch and dev elopm ent has pas sed , I T s ect or has b eco me suffi cie nt eno ugh t o
develop advanced software programming for even space exploration.
Programming languages in the beginning were very complex and were not feasible to achieve
larger calculations, Hardware was costly and was very limited in its capacity to perform continuoustasks, and Networking bandwidths was a gen next topic.
But Now Object oriented Programming languages, Terra bytes of memory and bandwidths of hundreds
of M bps, are the foundations for future's interactive web generation. Sites like Google, MSN and Yahoo
make life much easier to live with Chat , Conferencing and Data management etc.
So coming back to our goal (testing) , We need to realize that Software is here to stay and become a
part of mankind. Its the reality of tomorrow and a necessity to be learnt for healthy survival in the
coming technological era. More and more companies are spending billions of cash for achieving the
limits and in all these process one thing is attaining its place more prominently which is none other than
QUALITY.
I used so much of background to stress quality because Its the final and direct goal of Quality
assurance people or Test engineers.
l Quality can be defined as Justification of all of the user's requirements in a product with the
presence of value & safety.
So as you can see that quality is a much wider requirement of the masses when it comes to consumption
of any service, So the Job of a Tester is to act like a user and verify the product Fit ( defect free =
quality ).
l Defect can be defined as deviation from a users requirement in a particular product or service. So
the same product have different level of defects or No defects based on tastes and requirements of
different users.
As more and more busi ness solutio ns a re m ovin g fr om man to m achine , both deve lopment and testing
are headed for an unprecedented boom. Developers are under constant pressure of learning and
updating themselves with the latest programming languages to keep up the pace with user 's
requirements.
As a re su lt , Te st in g is al so be co mi ng an In te gr al pa rt of So ft wa re co mp an ie s to pr od uc e qu al it y
results for beating the competition. Previously developers used to test the applications besides coding,
but th is ha d di sa dv an ta ge s , Li ke ti me co ns um pt io n , em ot io na l bl ock to fi nd de fect s in on e's ow n
creation and Post delivery maintenance which is a common requirement now.
So Finally Testers have been appointed to simultaneously test the applications along with the
development , In order to identify defects as soon as possible to reduce time loss and improve
efficiency of the developers.
Who c an do it? Well, Anyone can do it. You need to be a graduate to enter software testing and
comfortable relationship with the PC. All you have to get in your mind is that your job is to act like a
third person or end user and taste (test) the food before they eat , and report it to the developer.
We a re not corr ect ing the mistake here, we are only identifying the defects and r eportin g i t and waitingfor the next release to check whether the defects are rectified and also to see whether new defects have
raised.
Some Important terminologies
l Project : If something is developed based on a particular user/users requirements, and is used
exclusively by them, then it is known as project. The finance is arranged by the client to complete
the project successfully.
l Product : If something is developed based on company's specification (after a general survey of
This week:
pageviews 427
Totals:
pageviews
comments
25677
17
7/28/2019 Knol 1
http://slidepdf.com/reader/full/knol-1 3/11
the market requirements) and can be used by multiple set of masses, then it is known as a product.
The company has to fund the entire development and usually expect to break even after a
successful market launch.
l Defect v/s Defective : If the product is justifying partial requirements of a particular customer
bu t is us ab le fu nc ti on al ly , th en we sa y th at Th e pr od uc t has a de fe ct , Bu t If th e pr od uc t is
functionally non usable , then even if some requirements are satisfied, the product still will be
tagged as Defective.
l Quality Assurance : Quality assurance is a process of monitoring and guiding each and every
role in the organization in order to make them perform their tasks according to the company's
process guidelines.
l Quality Control or Validation : To check whether the end result is the right product, In other
wor ds whe the r the deve lop ed serv ice meet s all the requ irem ent s or not .
l Quality Assurance Verification : It is the method to c heck whether the developed product or
project has followed the right process or guidelines through all the phases of development.l NCR : Whenever the role is not following the process in performing the task assigned, then the
penalty given to him is known as NCR ( Non Confirmacy raised).
l Inspection : Its a process of checking conducted by a group of members on a role or a
department suddenly without any prior intimation.
l Audit : Audit is a process of checking conducted on the roles or a department with a prior notice,
well in adva nce.
l SCM : Software configuration management : This is a process carried out by a team to attain
the following things Version control and Change control . In other terms SCM team is responsible
for updating all the common documents used across various domains to maintain uniformity, and
also name the project and update its version numbers by gauzing the amount of change in the
application or service after development.
l Common Repository : Its a server accessible by authorized users , to store and retrieve the
information safely and securely.l Base lining vs publishing : Its a process of finalizing the documents vs making it available to all
the relevant resources.
l Release : Its a process of sending the application from the development department to the testing
department or from the company to the market.
l SRN ( Software Release Note ) : Its a note prepared by the development department and sent to the
testing department during the release and it contains information about Path of the build,
Installation information, test data, list of known issues, version no, date and credentials etc.,
l SDN ( Software delivery Note ) : Its a note prepared by a team under the guidance of a Project
manager, and will be submitted to the customer during delivery. It contains a carefully crated User
manual and list of known issues and workarounds.
l Slippage : The extra time taken to accomplish a task is known as slippage
l Metrics v/s Matrix : Clear measurement of any task is defined as metrics, whereas a tabular
format with linking information which is used for tracing any information back through referencesis called as Matrix.
l Template v/s document : Template is a pre-defined set of questionnaire or a professional fill in
the blanks set up , which is used to prepare an finalize any document. The advantages of template is
to maintain uniformity and easier comprehension, throughout all the documentation in a Project,
group, department , company or even larger masses.
l Change Request v/s Impact Analysis : Change request is the proposal of the customer to bring
some changes into the project by filling a CRT ( ch ange request template). Whereas Impact analysis
is a study carried out by the business analysts to gauze , how much impact will fall on the already
developed part of the application and how feasible it is to go ahead with the change or demands of
the customer.
Software Development Life Cycle (SDLC)
This is a nothing but a model which is used to achieve efficient results in software companies and
consists of 6 main phases. We will discuss each stage in a descriptive fashion, dissected into four parts
individually, such as Tasks, Roles , Process and Proof of each phase completion. Remember SDLC is
similar to waterfall model where the output of one phase acts as the input for the next phase of the
cycle.
Initial phase
Analysis phas e
Design phase
Coding phase
Testing phase
Delivery and Maintenance
Initial-Phase/
Requirements phase :
Task : Interacting with the
c u s t o m e r a n d g a t h e r i n g t h e
requirements
Roles : Business Analyst and
Engagement Manager (EM).
Process : First the BA will take an
appointment with the customer,
7/28/2019 Knol 1
http://slidepdf.com/reader/full/knol-1 4/11
Collects the requirement template,
m e e t s t h e c u s t o m e r , g a t h e r s
requirements and comes back to the
co m p a n y wi t h t he r e qui r e m e n t s
document.
Then the EM will go through th e requirements document . Try to find additional requirements , Get the
prototype ( dummy, similar to end product) developed in order to get exact details in the case of
unclear requirements or confused customers, and also deal with any excess cost of the project.
Proof : The Requirements document is the proof of completion of the first phase of SDLC .
Altern ate nam es of the Requirem ents Document :
(Various companies and environments use different terminologies, But the logic is same )
FRS : Functional Requirements Specification.
CRS : Customer/Client Requirement Specification,
URS : User Requirement Specifications,
BRS : Business Requirement Specifications,
BDD : Business Design Document,
BD : Business Document.
Analysis Phase :
Tasks : Feasibility Study,
Tentative planning,
Technology selection
Requirement analysis
Roles : System Analyst (SA)
Project Manager (PM)
Technical manager (TM)
Process : A d e t a i le d s t u d y o n t he r e q u i r e m e nt s a n d
judgin g the po ss ib il it ie s an d scope of the re quiremen ts is
known as feasibility study. It is done by the Manager level
teams usually. After that in the next step we move to a
temporary scheduling of staff to initiate the project, Select a
suitable technology to develop the project ef fect ively
( customer 's choice is given f irst preference , If i t is
feasible ).
And Fina lly the Hard ware , soft ware and Huma n resou rces requ ired are list ed out in a docu ment
to baseline the project.
Proof : T h e p r o o f d o c u m e n t o f t h e a n a l y s i s p h a s e i s SRS ( System Requirement
Specification.)
Design Phase :
Tasks : High level Designing (H.L.D)
: Low level Designing (L.L.D)
Roles : Chief Architect ( handle HLD )
: Technical lead ( involved in LLD)
Process : The Chief Architect will divide the whole project into modules by drawing some graphical
layouts using Unif[ied Modeling Language (UML). The Technical lead will further divide those modules
into sub modules using UML . And both will be responsible for visioning the GUI ( The screen where
user interacts with the application OR Graphical User Interface .) and developing the Pseudo code (A
dummy code Or usually, Its a set of English Instructions to help the developers in coding the
application.)
Coding Phase :
Task : Developing the programs
Roles: Developers/programmers
Process : The developers will take the support of technical design document and will be following the
coding standards, while actual source code is developed. Some of the Industry standard coding
methods include Indentation, Color coding, Commenting etc.
Proof : The proof document of the coding phase is Source Code Document (SCD).
Testing Phase :
Task : Testing
Roles : Test engineers, Quality Assurance team.
Process : Since It is the core of our article , we will look at a descriptive fashion of understanding the
SDLC Image See ref erence s belo w
Analysis Image references see below
7/28/2019 Knol 1
http://slidepdf.com/reader/full/knol-1 5/11
testing process in an I T environment.
l First, the Requirements document will be received by the testing department
l The test engineers will review the requirements in order to understand them.
l While revisin g , If at al l an y doubts arise, then the teste rs will list out all the unclear r equirements in
a document named Requirements Clarification Note (RCN).
l Then they send the RCN to the author of the requirement document ( i.e, Business Analyst ) in
order to get the clarifications.
l Once the clarifications are done and sent to the testing team, they will take the test case template
and write the test cases. ( test cases like example1 above).
l Once the first build is released, they will execute the test cases.
l Whil e executing the test case s , If a t al l they f ind any defects, they will report i t in the Defect Profi le
Document or DPD.
l Since the DPD is in the common repository, the developers will be notified of the status of the
defect.
l Once the defects are sorted out, the development team releases the next build for testing. And also
update the status of defects in the DPD.
l Testers will here check for the previous defects, related defects, new defects and update the DPD.
Proof : The last two steps are carried out till the product is defect free , so quality assured product is
the proof of the testing phase ( and that is why it is a very important stage of SDLC in modern times).
Delivery & Maintenance phase
Tasks : Delivery
: Post delivery maintenance
Roles : Deployment engineers
Process : Delivery : The deployment engineers will go to the customer environment and install the
application in the customer's environment & submit the application along with the appropriate release
notes to the customer .
Maintenance : Once the application is delivered the customer will start using the application,
Wh ile us in g if an y prob le m oc curs , then it be co me s a ne w ta sk , Ba se d on th e se veri ty of th e is sue
corresponding roles and process will be formulated. Some customers may be expecting continuous
maintenance, In that case a team of software engineers will be taking care of the application regularly.
Software Testing Methods & Levels of Testing.
There are three methods of testing , Black Box, White Box & Grey box testing, Let's see.
Black Box testing : If one performs testing only on the functional part of an application
(where end users can perform actions) without having the structural knowledge, then that method
of testing is known as Black box testing. Usually test engineers are in this category.
Whit e Box test ing : If one performs testing on the structural part of the application then that
method of testing is known as white box testing. Usually developers or white box testers are the
ones to do it successfully.
Grey Box testing : If one performs testing on both the functional part as well as the structural
part of an application, then that method of testing is known as Grey box testing. It's an old way of
testing and is not as effective as the previous two methods and is l osing popularity recently.
Levels of Testing
There are 5 levels of testing in a software environment. They are as follows,
Im age: Systematic & Simultaneous Levels of testing. (The
ticked options are the ones where Black box testers are required and theother performed by the developers usually).
Unit level testing: A unit is defined as smallest part of an application. In this level of testing, each
and every program will be tested in order to confirm whether the conditions, functions and loops
etc are working fine or not. Usually the white box testers or developers are the performers at this
level.
7/28/2019 Knol 1
http://slidepdf.com/reader/full/knol-1 6/11
Module level testing: A module is defined as a group of related features to perform a major task.
At t his level th e module s are sent t o the testin g de partment and the test engi neers wi ll be validating
the functional part of the modules.
Integration level testing: At this level the developers will be developing the interfaces in order
to integrate the tested modules. While Integrating the modules they will test whether the interfaces
that connect the modules are functionally working or not.
Usually, the developers opt to integrate the modules in the following methods,
l Top down Approach: In this approach the parent modules are developed first and then the
corresponding child modules will be developed. In case while integrating the modules if any
mandatory module is missing then that is replaced with a temporary program called stub, to
facilitate testing.
l Bottom up approach: In this approach the child modules will be developed first and will beintegrated back to the parent modules. While integrating the modules in this way, if at all any
mandatory module is missing, then that module is replaced with a temporary program known
as driver to facilitate testing.
l Hybrid or Sandwich approach: In this approach both the TD & BU approaches will be
mixed due to several reasons.
l Big Bang approach: In this approach one wait till all the modules are developed and
integrate them finally at a time.
System Level testing :
Argu ably , the Core of the testi ng comes in this leve l. Its a major phas e in this testi ng leve l,
because de pend ing on the requirement and affo rd-abili ty of the company, Automat ion testing,
load, performance & stress testing etc will be carried out in this phase which demands additional
skills from a tester.
System: Once the stable complete application is installed into an environment, then as a whole it
can be called as a system (envt. + Application)
At SLS leve l, the test engi neer s wil l perfo rm many diff eren t type s of test ing, but the most Impo rtan t
one is,
System Integration Test: In this type of testing one will perform some actions on the modules
that were integrated by the developers in the previous phase, and simultaneously check whether
the reflections are proper in the related connected modules.
Example 2: Let's take An ATM machine application, with the modules as follows,
Welcome scre en, Bala nce inqu iry scre en, With draw al scre en & Depo sit scre en.
Ass umin g tha t the se 4 modu les wer e int egra ted by the deve lop ers, So bla ck box test ers can
perform System Integration testing like this :-
Test case 1:
Check Balance: Let's say amount is X
Deposit amount: Let's say amount is Y
Check balance: Expected Value
If the Actual Value is X + Y, then it is equal to the Expected Value. And because EV = AV, the result
is PASS.
User Acceptance Level Testing:
At th is level the user will be invited and in hi s pre sence, testing will be carried on . It s the final testi ng
befo re user signs o ff a nd a ccepts the appl ication . Whatever user may desi re, the corresponding feat ures
need to be tested functionally by the black box testers or Senior testers in the project.
Types of Testing:
There are two categories broadly to classify all the available types of testing software. They are Static
testing & Dynamic testing. Static means testing where No actions are performed on the application,
and features like GUI and appearance related testing comes under this category. And Dynamic is where
user needs to perform some actions on the application to test like functionality checking, link checking
etc.
Initially there were very few popular types of testing, which were lengthy and manual. But as the
applications are becoming more and more complex, Its inevitable that, not only features , functional ity
and appearance but performance and stability also are major areas to be concentrated.
The following types are the most is use and we will discuss about each of them one by one.
Build Acceptance Test/Verification/Sanity testing (BAT) : Its a type of testing in which one
wil l pe rform an overall test ing on the appl icat ion to vali date whether it i s proper for furt her deta iled
testing. Usually testing team conducts this in high risk applications before accepting the application
from the development department.
Other two terms Smoke testing and Sanity testing are in debate from time immemorial to find a fixed
definition. Majority feel that If developers test the overall application before releasing to the testing
team for further action is known as Smoke testing and future actions performed by black box test
engineers is known as Sanity testing. But this is cited as vice versa.
7/28/2019 Knol 1
http://slidepdf.com/reader/full/knol-1 7/11
Regression Testing : Its a type of test ing in one wi l l perform test ing on the already tested
functionality again and again. As the name suggests regression is revisiting the same functionality of a
feature, but it happens in the following two cases.
Case1 : When the test engineers find some defects and report it to the developers, The development
team fixes the issue and releases the next build. Once the next b uild is released, as per the requirement
the testers will check wether the defect is fixed, and also whether the related features are still working
fine which might have been affected while fixing the defect.
Example 3: Lets say that you wanted a bike with 17" tyres instead of 15" and sent the bike to the
service center for changing it. Before sending it back for changing, you tested all the other features and
yo u are sa ti sfi ed wi th them . Onc e the bi ke is ret urn ed to yo u wi th new ty re s, yo u wi ll also chec k the
look and feel overall, and check whether the brakes still work as expected, whether the mileage
maintains its expected value and all related features that can be affected by this change. Testing the tyre
in this case is New testing and all the other features will fall under Regression testing. Case 2 : Whenever some new feature is added to the application in the middle of development, and
released for testing. The test engineers may need to check additionally all the related features of the
newly added feature. In this case also all the features except the new functionality comes under
Regression testing.
Retesting : Its a type of testing in which one will perform testing on the same functionality again and
again with multiple sets of data in order to come to a conclusion whether its working fine or not.
Example 4: Lets say the customer wants a bank application and the login screen must have
the password field that only accepts alphanumeric (eg. abc123, 56df etc) data and no special characters
( *,$,# etc). In this case one needs to test the field with all possible combinations and different sets of
data to conclude that the password field is working fine. Such kind of repeated testing on any feature is
called Retesting.
Alp ha Te st ing & Bet a Te st ing : These are both performed in the User acceptance testing phase, If
the customer visits the company and the comapny's own test engineers perform testing in their own
premises, then it is referred as Alpha testing.
If the testing is carried out at the client's environment and is carried out by the end users or third party
test experts, then it is known as Beta testing . ( Remember that both these types are before the actual
implementation of the software in the clients environment, hence the term user acceptance. )
Installation Testing : Its a type of test ing in which one wi l l install the applicat ion into the
environment by following the guidelines given in the Deployment document / Installation guide. If at
all the installation is succesful then one will come to a conclusion that the installation guide and the
instructions in it are correct and it is appropriate to install the application, otherwise report the
problems in the deployment document.
One main point is to ensure that, In this type of testing we are checking the user manual and not the
product. ( i.e, the installation/setup guide and not the application's capability to install.)
Compatibility testing : Its a type of testing in which one will install the application into multiple
environments prepared with different combinations or environmental components in order to check
wh et he r th e ap pl ic at io n is su it ab le wi th th os e en vi ro nm en ts or no t. Us ua ll y th is ty pe of te st in g is
carried out on products rather than projects.
Monkey Testing : Its a type of testing in which Abnormal actions are performed intentionally on the
application in order to check the stability of the application. Remember it is different from stress testing
or load testing. We are concentrating on the stability of the features and functionality in the case of
extreme possibilities of actions performed on the application by different kind of users.
Useability Testing : In this kind of testing we will check the user freindliness of the application.
Depending on the complexity of the application, one needs to test whether information about all the
features are understandable easily. Navigation of the application must be easy to follow.
Exploratory Testing : Its a type of testing in which domain experts ( knowledge of business &
functions) will perform testing on the application without having the knowledge of requirements just by
parallely exploring the functionality. If you go by the simple definition of exploring, It means having
minimum idea about something, & then doing something related to it in order to know something more
about it.
End to End Testing : Its a type of testing in which we perform testing on various end to end
scenarios of an application. Which means performing various operations on the applications like
different users in real time scenario.
Example 5 : Lets take a bank application and consider the different end to end scenarios that exist
with in the applicat ion. Scen ario 1 : Logi n, Bala nce enqu iry , & Logo ut.
Scenario 2 : Login, Deposit, Withdrawal & logout.
Scenario 3 : Login, Balance enquiry, Deposit, Withdrawal, Logout. etc.
Security Testing : Its a type of testing in which one will test whether the application is a secured
application or not. In order to do the same, A black box test engineer will concentrate on the following
types of testing.
l Authentication Test ing : It is a type of testing in which one will try to enter into the application
by en teri ng di ff eren t co mbin at io ns of us erna mes an d pa sswo rd s in orde r to check wh ethe r the
application is allowing only the authorized users or not.
7/28/2019 Knol 1
http://slidepdf.com/reader/full/knol-1 8/11
l Direct URL testing : It is a type of testing in which one will enter the direct URL's ( Uniform
resource locator) of the secured pages and check whether the application is allowing the access to
those areas or not.
l Firewall Leakage testing : Firewall term is a very widely misunderstood word and it generally
means a barrier between two levels. ' The definition comes from an Old African story where people
used to put fire around them while sleeping, in order to prevent red-ants coming near them. ' So In
this type of testing, One will enter into the application as one level of user ( ex. member, ) and try to
access other higher level of users pages (ex. admin ,) , In order to check whether the firewalls are
work ing fine or not.
Port testing: Its a type of testing in which one will install the application into the clients environment
and check whether it is compatible with that environment. ( According to the requirements, one needs
to find what kind of environment is needed to be tested, whether it is product or project etc .)
Soak Testing/Reliability testing : Its a type of testing in which one will perform testing on the
application continuosly for long period of time in order to check the stability of the application.
Mutation testing : Its a type of testing in which one will perform testing on the application or its
related factors by doing some changes to the logics or layers of the environment . ( Refe r envt . knol for
details ) Any thing from the functionality of a feature to the applications overall route can be tested with
different set of combinations of environment.
Adho c test in g : Its a type of testing in which the test engineers will perform testing in their own style
after understanding the requirements clearly. ( Note that in Exploratory testing the domain experts do
not have the knowledge of requirements whereas in this case the test engineers have the expected
values set. )
Continuation :
The remaining Chapters are indexed below and are published on seperate knols. This is to maintain
the size of the knol to under 15-20 pages for easy management. If you are unable to find the knols,
please click on the author name and visit the knols list published by me.
Sub Index :
Environments
Software testing life cycle
Bug life cycle
ISTQB Certification syllabi and papers
Automation testing . (Under r evis ion ETA 02/28/09)
Performance testing
Quicktest proffesional VBScript. ( Under revision ETA 02/25/09)
Quality Center. (unpublished draft proofreading due. ETA ..02/09)
References
1. Image Analysis_speedo.png,Net savvy.com 2008 Retreived on 29/12/2008 .
Analysis image url
2. SDLC image jpg format, [email protected], retreived on 18/12/2008, OIW.com
bp2.blogger.com
3. Heartfelt thanks to Mr Suresh Reddy at NRSTT Hyderabad , My testing mentor, without whose support
this article would not have been possible. 2009
Mr Suresh Reddy at NRSTT Hyderabad
4. ISTQB1,4,5 Beizer , B (1990) Software Testing Technique, 2nd edition, Van Nostrand Reinhold:Boston
5. ISTQB2,6 coupland, L. (2003) A practitioners guide to software test design, Artech House
6. ISTQB3 Gilb, T & Graham, D (1993) Software Inspection, Addison-Wesley: London Hatton, L. (1997)
'Reexamining the Fault Density-component Size Connection' in IEEE Software, vol. 14 Issue 2, March
197; pp. 89-97.
7. ISTQB3, Van Veenendaal, E. (2004). The Testing Practitioner, 2nd edition, UTN publishing van
Veenendaal, E. and van der Zwan, M. (2000) 'GQM based Inspections' in proceedings of the 11th
European software control and metrics conference (ESCOM), Munich, May 2000.
8. ISTQB4, Broekman, B. and Notenboom, E. (2003) Testng Embedded software, Addison Wesley
9. ISTQB5 Black, R. (2001) Managing the testing process, 2nd edition, john wiley & sons: New York.
10. ISTQB6, Buwalda, H. Jaanssen, D & Pinkster, I. (2001) Intergrated Test Design and Automation, Addison
Wesley
Software Testing Courses100% Online Testing Courses Request
More Information Today!
Rational Training ClassesFunctionalTester, PerformanceTester
Robot, Quality Manager courses - NY
Comments
Sign in to write a comment
7/28/2019 Knol 1
http://slidepdf.com/reader/full/knol-1 9/11
knowledge in testing
Report abusive comment
Anonymous
Hi Vinayak,
I was a S/W engg having 2 yrs of exp. then I got the chance to come to testing on
financial domain which is dealing with US retirement plan. Since I am new to testing
world, so i am going through the Knol and trying to understand the testing process. In
the mean time I want to take ISTQB fundamental exam. Can you please give me how
should I proceed for the exam as well as to increase my knowledge in testing?
Regarding the knowledge in automation, right now I am doing manual, so I dont have
much idea. But I want to learn those tools. Can you please guide me how should I
proceed to learn those tools by my own? or which tool I should learn in the beginning
which has a good demand also?
Please assist me here.
Thank you
Post reply to this comment ▼ +6
Last edited Jun 13, 2009 3:48 PM
Nice Article -Need clarification regarding Alpha testing.
Report abusive comment
Rajamanickam Antonimuthu
Nice Article. Please check whether your definition for alpha testing is
correct.
You have mentioned that alpha testing will be done by "company's own
test engineers ". But my current understanding is alpha testing will be
done by the customer.
Post reply to this comment ▼ 0
Last edited Jun 13, 2009 5:38 AM
Hats Off!!!!!!!!!!
Report abusive comment
Hiten Shah
Hi Vinayak,
Hats off!!! to you...You have done a great job...
I liked the way you have explained Testing with simple examples/scenarios...
I have just begun my studies for ISTQB Foundation Level exam and this would help me
a lot...
Regards
Hiten
View/post replies (1) to this comment ▼ 0
Last edited Jun 7, 2009 5:13 AM
really wonderful information
Report abusive comment
michael
really wonderful information.
Michael [email protected]
Thank You !
Post reply to this comment ▼ 0
May 13, 2009 11:37 PM
Great info
Report abusive comment
Hunter
Well done! This information was much more detailed and simplier than the information I
have gotten from Uni.
Regards,
Hunter
w: www.ewebmarketing.com.au
Post reply to this comment ▼ -2
May 4, 2009 7:55 PM
7/28/2019 Knol 1
http://slidepdf.com/reader/full/knol-1 10/111 - 10 of 15 Older comments » Show all comments
Perfect collection
Report abusive comment
Anonymous
Vinayak, this is a perfect collection for testing and related studies
Post reply to this comment ▼ +1
Last edited Mar 12, 2009 2:14 AM
Amazing Information
Report abusive comment
Anonymous
Brilliant summary of Software testing , I guess this would make testing a very fun
oriented subject and easy to learn
Post reply to this comment ▼ -2
Last edited Mar 2, 2009 10:08 AM
This was an awsome presentation of valid information!! kudos
Report abusive comment
Anonymous
Hi Vinayak,
Inpsired by this thoughtfull flow of information from you on this topic has made me
mesmerised with the idea of taking up a career in this field.I have a query to you on this
note, as I am a software engineer by profession with 2 plus yr experience would like to
know.. if a person needs to identify with this new field of work area, what wud he/sheneed to do to qualify for oppurtunites in Testing,as I currently in working in anthr
dimension, software development work, from which i Like to move on to testing as I
have been provided with this exposure during my career.Kindly provide the guidelines
for candidates interested in domain migration.Will anISQTB certicate help help in taking
up a career full fledge in testing ?
Assuming the certificate is gained, will ISQTB certified professional with min 1.5 yrs
experiece in QTP and test cycle, help suffice the person to get absorbed in a testing
career?
Please provide your inputs as it priovide a gud knowledge of steps necessary to be
taken.
Thanks
Asha
View/post replies (1) to this comment ▼ +2
Last edited Feb 9, 2009 8:08 AM
Good work......keep it up
Report abusive comment
suresh sa
hi vinayak,
Thanks for your sharing your view about Testing. Really is a very good one than whatever
i read till now. please keep it up this. will be very useful to all.
really am very proud of you....
what like in yours than others.
* your way of explanation is very clear and understandable. i thing this is a main objective
of any book or guide.
Please keep it up this way........
note:
need one more info from you if you have any Material or document about ISTQB please
send to my mail ID: [email protected]
Suresh.
Post reply to this comment ▼ 0
Last edited Jan 18, 2009 11:02 PM
Thanks for Sharing Information
Report abusive comment
P Uday Kumar
Thanks Vinayak for sharing information! It was really helpful for me to understand the
concept of testing.
Hope to see some more articles from you in future.Thanks once again...
Post reply to this comment ▼ 0
Last edited Dec 22, 2008 10:26 PM
7/28/2019 Knol 1
http://slidepdf.com/reader/full/knol-1 11/11
Home | Terms of Service | Privacy Policy | Content Policy | Help
©2009 Google
