Upload
avumaa22
View
218
Download
0
Embed Size (px)
Citation preview
7/28/2019 Testing Life Cycle and Software Development Life Cycle
1/15
Testing Life Cycle and Software Development Life Cycle
TO develope a software in general we are following SDLC process means Software Developemnet Life Cycle in thi
ycle we are going to face different stages likeBRS/SRS document preparation, Software Analysis, Software Coding, Integartion Testing, Software Testing, User
Acceptance Testing
Relese and maintainanceWhere as in STLC means Software Testing Life Cycle for conducting Software testing process in SDLC we are
following this.
Means this STLC is one of the stage in the SDLC process
Agian in STLC we will follow some stages likeTest methodology / strategy, Test Plan ,Test design(Test scenarios and test acses prepartion), Test excution
Test reporting
Preparing Test Responsibilty Matrix
Testing is a part of Software Development Life Cycle
difference between alpha Testing and beta testing
Let me explain about these two types of testing.Both of these testings are done by clients only. Only difference is the place where the testing takes place.
n Alpha testing client comes to testing environment and will do testing while 80 of the application has been develop
and tested
n Beta testing complete application package will be installed in client environment (ie) Real time environment and
do testing in the application which is completed (100 ) development and testingOnce software gets completed will testing and retesting then it needs to pass from 2 more phases ie Alpha and Beta
esting.
Alpha : Performed by the testers or users at development site and it's considered as internal acceptance testing to go
Beta testing if at all any issues found immly devs will fix those issues.
Beta: It comes after alpha testing can done by limited no.of external users or by customers in a real time environme
an have versions in every versions found bugs were fixed.
nformal Test StrategyThe test strategy that is informal and non structured is known as _______________
nformal non-structured testing is called 'ad-hoc testing' or 'exploratory testing'.
Test 5 Screens of an Application What type of testing you can do? When we gave you 5 screens and, how can y
est that application?f testing is being done for User Acceptance Testing, then all the functioning from user point of view is being testedesting the overall functioning, validations, gramatical errors, by filling all type of values with every permutation an
ombination by looking overall UI.
First of all i can do the Exploratory testing to learn the functionality it self and the report the issues if came.
And if there is time then i can for full fledge functiponal testing along with usability testing.
Based on the requirement I will select the testing. For the beginning I will do the exploratory testing to know the
functionality. Then I will check whether it is accepted for the links is there any cosmetic defects and spell check if ths any db connectivity means boundary value equvalence partitioning etc.
RE: Testing Cycle and Testing Process
Testing cycle is nothing but test life cycle (STLC). In this we have requirements test plan test case designing test capreparation and test execution.
Testing process means how to process the life cycle. In test management decides which software they are going to
use(testing tools middleware communications etc. ) how many testers do they need for the project how much moneyare going to spend etc.
Testing Cycle: This is nothing but stags involved of complete testing
7/28/2019 Testing Life Cycle and Software Development Life Cycle
2/15
n general Testing cycle has following stages.
> Req review-> Test case preparation-> Test case execution-> Result analysis-> Reporting
Testing Process: This indicates how we are going to test an application
> Unite testing-> Module Testing-> Integration Testing-> System Testing-> UAT
Next : Alpha and Beta
And then Regression testing if needs
sting cycle is the way the testing stage is performed.
The Testing cycle is as follows:Test case preparation.
Test case review.
Test case execution.Defect identification and reporting.
Test Report.
Testing process is a testing management kind of work. As the term goes:TESTING (the test action to be performed on a product) and PROCESS (the planning done to perform testing)
So it starts before the testing commences. The person responsible for the testing process should work along with the
development team from the time of estimation prepared for the product to know what is the estimation, understand tnvironment and get the required details for the set up, identify test person skills and identify and train people prior
esting commences, and preparing, monitoring testing schedule and work with the testing team to understand the pro
tatus and report on the testing status. So testing process is somewhat equivalent to the development process.
RE: Your Customer does not know how to write UAT documents How will you Handle this situation?
think most of the custemors definitely know about how to write UAT and all...in worst case if he doesn't know the
an help him as how to do the acceptance testing and what should it contains ie ask him to prepare thetest cases for tfunctional part of application and what exactly he needs from the application.
Well a Tester can help Customer to Design User Acceptance Test Cases. Normally use cases are created during the
equirements definitions phase of a project. Mainely USer Acceptance Test Cases must be concentrated and addressuser's(Customer's) functional needs.UAT Test Cases should be designed with considering points like customer exac
needs User environments User simultenious loads etc etc.
Acid Testing I have come across the Term "Atomicity, Consistency, Isolation, Durability" acronym as ACID ,
any one have more knowledge about this Testing strategy... Help would be Appreciated
Basically in IT World ACID is acronym of Atomic Consistent Isolation Durable. Which is specifically define aProperties of a Good Database Transaction.So I think ACID Testing is either a Database Testing. The white box and
Black box Testing of Database Queries/Processes.
How do you use boundary value analysis testing for evaluating the password
Boundary Value Analysis for testing password.
As per rule boundary value Analysis must have SIx Conditions MIN-1, MIN, MIN+1MAX-1, MAX, MAX+1
As per ref available for me from
http://softwaretestingguide.blogspot.com/for user id when can apply same for password it works like this
ets have condition password min 4 char max 10 char in length.password can be any thing since password depends o
userid.
2
7/28/2019 Testing Life Cycle and Software Development Life Cycle
3/15
MIN-1
User ID : masterpassword : abc
esult :Should not accept should popup msg "enter Correct Password".
MINUser ID : Master
password : abcd
esult : Should accept
MIN+1User ID : Master
password : abcd
esult : Should acceptMAX-1
User ID : Master
password : 123456789esult : Should accept
MAX
User ID : Masterpassword : abcd123456
esult : Should acceptMAX+1
User ID : Masterpassword : abcd1234567
esult : Should not accept should popup msg "enter Correct Password".
Firstly we have to identify that what is the BVA range of the password from the SRS Document/from the clientequirements and capture the min and max ranges
So according that we have to test by following min-1 min min+1 max-1 max max+1By following this we have to test for Boundary value analysis to evaluate that password
We should get the testing results asmin-1 (fail)min (pass)
min+1(pass)
max-1(pass)max(pass)
max+1(fail)
How would you prioritise your test and why?
Prioritising the tasks is the duty of Team lead if at all team lead assigns you to tasks at the same time and given som
ime in that case prioritise the tasks is team members duty.
For ex: If a team member having 2 tasks and need to start the testing at the same time first task for complete testing 2nd one is just retesting only one issue in this case i can choose retesting as first task and go for 2nd task
So finally i can say one thing prioritising the tasks is completely depends on experience and date of delivery.
Priority 1 (Immediate): The bug should be resolved immediately.
Priority 2 (High): This bug should be resolved as soon as possible in the normal course of development activity befohe software is released.
Priority 3 (Medium): This bug should be repaired after serious bugs have been fixed.
Priority 4 (Low): It can be resolved in a future major system revision or not be resolved at all.
7/28/2019 Testing Life Cycle and Software Development Life Cycle
4/15
What is the most important thing in a test case?
As for my knowledge a clean and neat 'Test case description' is the most important one in test case why because indescription a tester can found max idea of what we are going to do in the application.
FOr ex: Desc: Verify that proper validation message will be shown for blank user id.
BY reading this description a tester can easily under stod he has to check the user id for validation
The important thing is Test case id should be unique and test case description should be clear and it should describe
whole process of the test case
what is synchronization and what is the difference between synchronization and wait?Synchronization: Action should be take place in time manner (State field should accept after accept the Country fiel
ake this action Wait() function is used in scripts untill the State field is selected.
BOUNDARY VALUE ANALYSIS: It is a black box testing technique which is used to reduce the no.of test cases
est data to a manageble size by focusing on the boundaries basing on the assumption that false do occur mostly at th
boundaries
EQUIVALENCE PARTITION: It is a black box testing technique which is used to reduce the no.of test cases or t
data to a manageble size by dividing the i/p's or o/p's or preconditions into equivalent partition that consists a set of
or treated same by application that produce the same results.
Difference between static and dynamic testing? Is dynamic is functional?What is Spiral Model?Difference
between spiral model, v model and waterfall model?: Static testing is about prevention dynamic testing is about cure.
2: The static tools offer greater marginal benefits.
: Static testing is many times more cost-effective than dynamic testing.
4: Static testing beats dynamic testing by a wide margin.
5: Static testing is more effective!
6: Static testing gives you comprehensive diagnostics for your code.
7: Static testing achieves 100 statement coverage in a relatively short time while dynamic testing often often achieve
ess than 50 statement coverage because dynamic testing finds bugs only in parts of the code that are actually execut
8: Dynamic testing usually takes longer than static testing. Dynamic testing may involve running several test cases e
of which may take longer than compilation.
9: Dynamic testing finds fewer bugs than static testing.
0: Static testing can be done before compilation while dynamic testing can take place only after compilation and lin
1: Static testing can find all of the followings that dynamic testing cannot find: syntax errors code that is hard to
maintain code that is hard to test code that does not conform to coding standards and ANSI violations.
Ya Dynamic testing invoves functional testing also.
Spiral Model:
The spiral model is a software developement process combining elements of both design and prototyping-in-stages
4
7/28/2019 Testing Life Cycle and Software Development Life Cycle
5/15
ffort to combine advantages oftop down and botton up concepts. Also known as the spiral lifecycle model it is a sy
development method (SDM) used in(IT). This model of development combines the features of the prototyping mode
he water fall model. The spiral model is intended for large expensive and complicated projects
Diffrence between Spiral Model V Model and waterfall Model:
Spiral Model/V-Model are for large or complaicated projects.
n Spiral model / V-Model we are conducting cerification and validation at a time.
n waterfall model the validation will takes only at the last stage of before releasing a project.
what is a test scenario and test condition. What is the basic difference between the two ?Test Scenario:
Test Scenario is hypothetical story to help a person think through a complex problem or system for a testingnvironment. The ideal scenario has five key characteristics: it is (a) a story that is (b) motivating (c) credible (d)
omplex and (e) easy to evaluate.
.e) Flow of Data from one end to another end
Test Condtion:
Test Condition is nothing but which is mentioned in the Test Steps. which might be a Pre-Condition/Post-condtion.for example: If a Search Field displayes the List of Search results
Pre-Condition: The Search should display Search results(Records displayed in tables)Post-Condition: Records should display in next page if the searched results contains more than 10/20 records
Test scenario is the flow of the data from one end to another end ,
but the test condition is one which willl denote the condition of the test i.e whether it is passedor failed,or the
s still under the processing.
hat is ithe significance of v-model in software t...
n the realtime the cost of the project is very important here the cost means time so by using the v- model the
equirements can be developed well as the testing will occur at every stage there are less number of chanses for getthe errors inthe later stages the main aim of v- model is erradicating the errorsin the early states.
RE: What is Alpha testing and Beta testing?
Alpha testing is done before the release of a product to check whether it is functioning properly or not.Beta testing is done when the product is given to end users. They use it and if they find any defects in it they report b
o developers. This is done before the final release of the product.
RE: What is the difference between Smoke Testing and Adhoc Testing and if you are doing Smoke Testing th
why Adhoc Testing? Smoke testing - testing done to check the stability of the initial build when received fromdevelopers.
Adhoc testing - testing done on main functionalities due to lack of time.
ntially smoke testing is done whether the build is ready for further testing or not.checks the functionality of the buildAdhoc testing is done when lack of documentation and time.they are like buddy testing monkey testing all these are
adhoc testing
basically the adhoc testing is done with past experianceo of test engineers and genarally it is doe due to lack of propequirements, where as the smoke testing is done to known whether the build obtained is stable or not to perform the
esting.
Test Objective means Setting an goal before testing begins. It is measurable by the metrics you will be collecting a
nd of the test to assure that you have delivered a quality output. The metrics are cearly stated based on the past proj
5
7/28/2019 Testing Life Cycle and Software Development Life Cycle
6/15
xperiences and the complexity analysed.
For example :
Attaining 95% in Defect Removal Effectiveness is considered as overall healthy.Code Coverage of 80% in overall Testing
DD as 3.5 defects/KLOC
Delivering a quality software to customers with out any errors and along with super quality is the test objective
Test objective to give a quality product to the software i.e like Application S/W is working according to requiremen
mentioned by the clients or customers.We check its performance its security its functionality.
RE: What is meant by domain? What is domain testing?
omain: Its a specific area to which the project belongsDomain testing is nothing but conducting testing on diffrent domains relarted to variuos projects It varies based on p
area/Domain
Ex:
banking
Hospital
nsuranceE-retaiDomain: It is a field of study that defines a set of common requirements terminology and functionality for an
oftware program constructed to solve a problem in that field.
Different Software Domains:
Banking
Financensurance
E-Learning
ob PortalHealth Care
Shopping Portal etc..
Domain Testing: Tester should aware and clear cut knowledge in the Domain makes him work effective in the diffe
Domains.
etc
RE: What is testing methodology?Is is .. regression testing or its a part of regression? (which part bug check)
Testing methodology----testing the entire application to make sure that it follows all the specifications and requirem
Retesting---when a bug is found it will be assigned to the developer who can fix it. after removing the bug by devel
ester has to test with various inputs to make sure that the bug has been removed permanently. Regression testing--
while fixing bugs by developers some times source code changes will occur. Change in one portion of source code maffect other areas so in addition to retesting of the software tester has to execute a predefined set of test cases to mak
ure that the other areas are not affected is called regression testing.
RE: what are the difference between sanity and smoke testing.
The difference between a smoke and sanity testing is:
Smoke test verifies whether all components of the software are available and acceptible for testing when the softwa
first released to the test team.
6
7/28/2019 Testing Life Cycle and Software Development Life Cycle
7/15
Example: A software build is introduced to the test team and they run some cursory tests at a high level throughout t
application in order to determine whether it is acceptible for testing.
Sanity test verifies whether all components of the software are working properly after changes have been made. Th
ypically occurs during a test pass.
Example: The development team has introduced a fix in production and testers have been asked to perform a sanity
o ensure major functionalities have not been negatively impacted by the fix.
RE: What is Defect Density and how can we calculate Defect Density ?Defect density is a measure of the total known defects divided by the size of the software entity being measured.
Number of Known Defects
--------------------------------Size
The Number of Known Defects is the count of total defects identified against a particular software entity during a
particular time period. Examples include:
Defect to date since the creation of moduleDefects found in a program during an inspection
Defects to date since the shipment of a release to the customer
Size is a normalizer that allows comparisons between different software entities (i.e. modules releases products).Size is typically counted either in Lines of Code or Function Points.
Uses: Defect Density is used to compare the relative number of defects in various software components. This helps
dentify candidates for additional inspection or testing or for possible reengineering or replacement.
Defect density is a metric used to make informed decisions about software quality.
Defect density # of defects / unit or component size
The size is measured in:> Software lines of code (SLOC)
> Function points (FP)
This measure is often used to determine high-risk components that will require more attention in future projects. It i
used to provide a baseline for process improvements.
RE: what is the difference between Test Case and Test Script ?
what is the difference between usability testing & user acceptance testing?
UAT is a form of Acceptance testing conducted from the user's perspective.( i.e. involving User representatives) Thi
esting phase is used to test the system as a wholeto ensure that it meets its stated business requirements and that it
performs within defined constraints. This testing phase takes place after system testinghas been completed.
Usability testing a particular type of Nonfunctional Testing that focuses on the ease of use of the application under t
from the perspective of the End user. Issues to be considered inUsability testing include the intuitivesness consisten
and clarity or understandability of the user interface.
7
7/28/2019 Testing Life Cycle and Software Development Life Cycle
8/15
RE: What is Test Automation?
When we use a testing tool to generate and execute test cases then this testing called automated testing or test automConducting testing process with the help of automation testing tools is known as Test Automation i.e excution of te
ases on the software build
RE: Is the Static testing a functional testing?
Static testing is verification not validation.But functional testing is a validation activity to compare the actual result xpected.So static testing is not a functional testing or the question is just to confuse the candidate only.
Static testing is also a verification or inprocess reviewing.It means that the test is being performed without executingode.It will occur throughout the development phase in the form of reviews walkthroughs inspections
Functional testing is testing software based on its functional requirements. It ensures that the program physically wo
he way it was intended
Can the static testing be done for both Web & Client Server Application ?
Static testing doesn't depend upon the application so we can do static testing on web or client server application.
Yes We can do static testing since it is only verification testing
RE: List the Testing types, Testing methodologies, Testing Techniques and Testing Levels. How are all these ielated or placed under the overall Software Testing Process.
Testing Types:
. Unit testing2. Integration Testing
. Regression Testing
4. System testing
5. Acceptence Testing.6. Performance Testing
7. Load Testing
8. Stress Testing
9. Alpha Testing0. Beta testing
Testing Techniques:
. Black Box Testing
2. White box (or gray box) testing
Testing Levels:
Black box testing:
. Graph based testing2. Equivalence partiioning testing
. Boundry Value analysis testing.4. Comparision Testing5. Orthogonal Array testing.
What are main 5 types of test metrics? Explain in ...
thought that the types of Test metrics are as follows:
. USER APRTICIPATION - User participation test time Vs. Total Test time
8
7/28/2019 Testing Life Cycle and Software Development Life Cycle
9/15
2. PATH TESTED - No of paths tested Vs. Total Number of paths
. ACCEPTANCE CRITERIA TESTED - Acceptance Criteria verified Vs. Total Acceptance Criteria
4. TEST COST - Test Cost Vs. Total System Cost
5. COST TO LOCATE DEFECT - No of defects located in the testing. This metric shows the cost to locate a defect
6. DETECTED PRODUCTION DEFECT - No. of defects detected in production Vs. Application System size
7. TEST AUTOMATION - Cost of Manual test Effort Vs. Total Test Cost.
Pl. clarify. Thanks
RE: What is Cyclomatic complexity
Cyclomatic complexity gives the number of independant paths in a Program its denoted by a NumberTo find the independent paths in a program file
A measure of the logical complexity of an algorithm used in white-box testing.
Cyclomatic complexity V (G) for a flow graph G is equal to
1. The number of regions in the flow graph.
2. V (G) E - N + 2 whereEis the number of edges andNis the number of nodes.3. V (G) P + 1 wherePis the number of predicate nodes.
what is a test case identifier
A test identifier is referenced by the test design specification and the test procedure specifications. which identify a
ase uniquely.
E: what is meant by crs&urs explain breifly? ...
CRS is customer requirement specification and URS is user requirement specification.. both are same and they contahe business requirements in the form of raw data of the information domain
CRS: Client Requirement SpecificationHere Requirments are gathered up on Client points.
URS: User Requirement Specification.Here Requirments are gathered up on End User poins.
what is the difference between smoke testing and the built testing?
what is adhoc testing?
DIFF between revision and version?
In computer programmingsmoke testingis a preliminary to further testing which should reveal simple failures snough to reject a prospective software release. In this case the smoke is metaphorical.
Ad Hoc Testing: A testing phase where the tester tries to 'break' the system by randomly trying the system's
functionality. Can include negative testing as well.
9
http://www.geekinterview.com/question_details/35942http://www.geekinterview.com/question_details/359427/28/2019 Testing Life Cycle and Software Development Life Cycle
10/15
versions:This document describes the version numbering used in the Unicode Standard the nature of the Unicode
haracter repertoire and how to cite and reference the Unicode Standard the Unicode Character Database and Unico
Technical Reports.
Revision control (also known as version control orsource control) is the management of multiple revisions of the
ame unit of information. It is most commonly used in engineering and software development to manage ongoing
development of digital documents like application source code art resources such asblueprints or electronic models
other critical information that may be worked on by a team of people. Changes to these documents are identified byncrementing an associated number or letter code termed the revision number revision level or simply revision and
associated historically with the person making the change. A simple form of revision control for example has the inissue of a drawing assigned the revision number 1 . When the first change is made the revision number is increment
2 and so on.
udhakar kolla My email:[email protected] number:09819859346
Unit testing comes under which testing technique, white box / black box?
Yes it comes under white box tesing which normaly comes under the purview of the developers. Unit test normaly
preceds the testing by specialised testers.
fine quality in testing
To satify customer's functional and non-functional requirementsWhat's contain on the test strategy?
Test Strategy - defines the approach to be followed for testing a software.
t contains
.Scope and Objective2.Business Issues
.Responsibility Matrix
4.Roles and Responsibilities5.Communication and Status Reporting
6.Testing automation and testing tools
7.Defect Reporting and Tracking
8.Testing measurements and metrics
9.Risks and Assumptions
0.Change and Configuration management
1.Training needs
Test strategy describes how we are going to approach the testing interms of people tools procedures and support.
RE: What is Thinktime? What is Prevention ...
Thinktime:The time to create request by the client to send to server is called Think time.
0
http://www.geekinterview.com/question_details/35942http://www.geekinterview.com/question_details/35942http://www.geekinterview.com/question_details/35942http://www.geekinterview.com/question_details/35942http://www.geekinterview.com/question_details/35942http://www.geekinterview.com/question_details/35942http://www.geekinterview.com/question_details/35942http://www.geekinterview.com/question_details/35942http://www.geekinterview.com/question_details/35942http://www.geekinterview.com/question_details/359427/28/2019 Testing Life Cycle and Software Development Life Cycle
11/15
Prevention Testing:Build test cases based upon the requirements specification error to the creation of code with the
xpress purpose of validating the requirements.
) What is the differnece between Quality Analysis and Quality Control ?
2) Differentiate fault and failure
3) Differentiate product maturity model and capability maturity model
4) Explain with ex. a product based company and service based company
5? What is a) monkey testing , b) guerilla testing
Quality Analysis: This is nothing but validation process.here the bugs or defects which we call will be eliminated.
he process and standard documents and being prepared.here the reports that are prepared byquality control after tesare being implemented for reviews
Quality Control: This is a verification process.the process and the standard's documents that are prepared are being
mplemented.the reports are being prepared aftertesting.
Fault: An abnormal condition or defect at the component equipment or sub-system level which may lead to a failure
Failure: It general refers to the state or condition of not meeting a desirable or intended objective.
Monkey Testing: It is the random testing performed by the automation testing tools.
Gorilla Testing: Testing one particular module functionality heavily.
What is the difference between Test Bed and Test H...
Test bed : An execution environment configured for testing as hardware software networks etc.
Test harness : A programe or test tool used to execute a test. Also known as test driver.
est harness:it indicates readyness to start test execution
est harness test environment+test bed
est environment--->required hardware and software components for the test execution...
est bed---->required test cases which are ready for execution.
How u prepare Test Data? Is it from Functional Req...
est data prepared depends on srs if it is not clear then t.e will go to exploratory testing means past experience browson similar projects down loading or directly contacting with customer.test data is nothingbut that may be user define
equirement or functionality requirement.
Test Schedule :- If an application has 100 pages to be tested.How much time it will take?
How u caluculate?(It Depemds upon the Complexity of the functionlity is know factor)
The time taken for completion of an application will me measured using cyclomatic complexity.It is a quantitative
measure to calculate time.This depends upon the complexity of the pages. May be one page will be having only the content and other page ha
very complex financial calculations. The easy way of finding the time is to find the time of development of these
ndividual pages. And calculate 30-40 time of testing as per the time consumed in developement.
how can you take snapshot/screen shots in case of manual testing and how can you attach it to the test case?
1
7/28/2019 Testing Life Cycle and Software Development Life Cycle
12/15
For taking Snapshot/Screen shot you can use Print screen button and paste it in Paint and save as .jpeg file.
f you are using application for writing test cases you can attach the picture file to the test cases.
f you are usinf Excel for writing test cases you can paste the picture by using Insert-Picture (insert from File).One thing why you want to attach Snapshot/Screen shot for Test Case.
use print screen button and paste it in paint
attach against the specific test case in the comments column or if u r using test director or bugzilla we have a field a
attachment
What is the difference between SRS and BRS?
SRS: Software Requirements Specification . Srs is prepared by Software Analyst. They implement the BRS iN
preparation of Srs.
BRS: Business Requirement Specification. BRS is given by Client . It tells the business Logics .
EX: hOW TO CALICULATE cOMMISSION AND ON WHICH COMPONENT LIKE TAHT .
BRS-- Business requirement specification it is given by client only(all the client requirements would be there withou
proper procedure)
SRS--Software Requirement specification It specifies the all the requirements of the customer.
SRS is developed based on BRS only.
SRS is a Software /System Requirement specification it is a MS word doc. which defines the complete businessfunctionalities of the particular application
SRS designed by System Anallyst
BRS is a Business Requirement Specification Initially client will give the req's in their own format then it will beonverted in to Standard format by which s/w people can understand.
n BRS the req's are defined in general format. where as in SRS the req's will be divided in to modules and each moontains How many interfaces and screens like that
BRS is developed by Business Analyst
what is accessibility testing?recently i faced in TCS
What is difference between Integration testing & Inter system testing?
ntegration testing :it is the testing to see whether all the corresponding modules are correctly integrated or not.inter
yatem testing :our appliction is able to share the resources along with the other applications or not
ntegration Testing: Testing of combined parts of an application to determine if they function together correctly. Usuperformed after unit and functional testing. This type of testing is especially relevant to client/server and distributedystems.
nter system testing:
Intersystem parameters would be checked / verified after the change or new application is placed in the productio
Example
2
7/28/2019 Testing Life Cycle and Software Development Life Cycle
13/15
Develop test transaction set in one application and passing to another system to verify the processing.
Entering test transactions in live production environment and then using integrated test facility to check the
processing from one system to another.
Verifying new changes of the parameters in the system which are being tested are corrected in the document
E: what types of tests comes under black box testing
Various testing types that fall under the Black Box Testing strategy are: functional testing stress testing recovery tes
volume testing User Acceptance Testing (also known as UAT) system testing Sanity or Smoke testing load testingUsability testing Exploratory testing ad-hoc testing alpha testing beta testing etc.
These testing types are again divided in two groups: a) Testing in which user plays a role of tester and b) User is not
equired.
Testing method where user is not required:
Functional Testing:
n this type of testing the software is tested for the functional requirements. The tests are written in order to check if
application behaves as expected.
Stress Testing:
The application is tested against heavy load such as complex numerical values large number of inputs large number queries etc. which checks for the stress/load the applications can withstand.
Load Testing:
The application is tested against heavy loads or inputs such as testing of web sites in order to find out at what point tweb-site/application fails or at what point its performance degrades.
Ad-hoc Testing:This type of testing is done without any formal Test Plan or Test Case creation. Ad-hoc testing helps in deciding the
cope and duration of the various other testing and it also helps testers in learning the application prior starting with
other testing.
Exploratory Testing:
This testing is similar to the ad-hoc testing and is done in order to learn/explore the application.
Usability Testing:
This testing is also called as Testing for User-Friendliness . This testing is done if User Interface of the application s
an important consideration and needs to be specific for the specific type of user.
Smoke Testing:
This type of testing is also called sanity testing and is done in order to check if the application is ready for further mesting and is working properly without failing up to least expected level.
Recovery Testing:
Recovery testing is basically done in order to check how fast and better the application can recover against any typerash or hardware failure etc. Type or extent of recovery is specified in the requirement specifications.
Volume Testing:Volume testing is done against the efficiency of the application. Huge amount of data is processed through the
application (which is being tested) in order to check the extreme limitations of the system.
3
7/28/2019 Testing Life Cycle and Software Development Life Cycle
14/15
7/28/2019 Testing Life Cycle and Software Development Life Cycle
15/15
What is the difference between CMM & CMMI? If any....
hai....
CMM-is a way to develop and refine an organization's software development process.
CMMI-is a process improvement approach that provides organizations with the essential elements of effective proce
CMM->software Engineering organizations
CMMI->System Engineering & Software Engineering organizationsWho approved your test cases?
Test lead or we can baseline the testcases with pear reviews and some times client will aprove the test cases that dep
on the organisation's policy
fter reviewing the test cases. The Test Team Lead aproves the test cases.
Also it depends on the Organisation and the persons working under testing.
n some cases BA / PM also approves the Test Cases after review.
In an application currently in production, one module of code is being modified. Is it necessary to re- test thewhole application or is it enough to just test functionality associated with that module?
Frist u see the system design if that module is connected to any other module then u need to test both the modules elneed of testing entire system
) Test the modified module
2) Test all the other modules/areas of the application which will have direct/indirect interaction with the modified
module.
What is included in test strategy?
What is overall process of testing step by step and what are various documnets used testing during process?
What is the most challenging situation you had during testing
o reproduce the failed test cases environmentWell most of the part is challenging. From my side finding some show stopper bug while doing ADhoc testing.
5