BLACK BOX TESTING / CLOSED BOX TESTING / BEHAVIOURAL TESTING / FUNCTIONALITY TESTING

Globalization testing
Difference White Box testing Functional testing Integration testing System testing Acceptance testing Smoke testing Adhoc testing Exploratory testing Usability testing Performance testing Compatibility testing Regression testing Reliability Resting Recovery testing
I18N Testing L10N Testing
Testing each and every line of the Testing each and every components of an Testing the data flow or interface It is an End to end testing done by the It is an End to End Testing ,done by the Testing the Basic and Critical features of an Tesing the application or software randomly Understand the application, identify all possible Testing the User Friendliness of an application is Testing the Stability and Response Time of an Testing the SW which is developed for different Testing the sw / application if it is developed Testing the functionality of an Testing old or unchanged features to Testing the functionality of Testing thefunctionality of an
code is called White Box testing. application Rigorously/Thoroughly between two or more modules/features Test Engineer in Testing Endusers/Customers where in they use Software for application before doing Thorough/ without looking into the requirement is called as scenarios, document the scenarios & test the called Usability Testing. application by applying load is called Performance languages in called Globalization Testing for country standards / country culture is application / SW for different make sure that changes like adding a an application continuosly application to check how well the
against Customer Requirement is called as Integration Testing. Server/Environment which is similar to the real time business for some particular period of time Rigorously Testing is called as Smoke Adhoc testing application by refereing the document is called Testing. called Localization testing hardware & SW configurations is feature,removing a feature,modifying a for a particular period of SW recovers from crashes or
What Specification is called as Functional Production Server/ Environment. and check whether sw can handle all real time Testing. Exploratory testing called as Compatibility testing feature and fixing defects is not time is called Reability disaster is called as Recovery
Testing/ Component Testing. situations and scenarios. introdusing any defects in old or testing testing
unchanged features is called Regression
testing.
1) Requirement should be present. 1)Requirement should be present. 1)Requirement should be present. 1)Requirement should be present. 1)Requirement should be present. 1)As soon as we get the build we(TE) 1).As soon as we get the build 1).When there is no requirement 1)Requirement should be present. 1)Requirement should be present. 1)Requirement should be present. 1)Requirement should be present. Once after the SW is tested for the
2) Coding should be done. 2)Coding should be done. 2)Coding should be done. 3)WBT 2)Coding should be done. 2)Coding should be done. 3)WBT should do Smoke Testing. we should do smoke testing, since smoke is 2).Threre is requirement but TE dosen't have 2)Coding should be done. 3)WBT should be 2)Coding should be done. 3)WBT should be done. 2)Coding should be done. 3)WBT should be done. 2)Coding should be done. 3)WBT should base platform the SW can be
3)WBT should be done. should be done. 4)SW/Build should be 3)WBT should be done. should be done. 2)When Developer give the build to the positive testing here we should not do time to understand the req done. 4)sw/Build should be installed into server. 4)SW/Build should be installed into server. 4)sw/Build should be installed into server. be done. 4)sw/Build should be installed into tested for Compatibility
4)sw/Build should be installed into installed into server. 4)SW/Build should be installed into 4)sw/Build should be installed into server. Customer,chances are there developer might -ve testing(Adhoc) 3).Req is present but its very complex to 5)Resources should be available. 5)Resources should be available. 5)Resources should be available. server.
server. 5)Resources should be available. server. 5)Resources should be available. miss to copy few of the files,so customer will 2).While doing FT/IT/ST either in btw or at understand 6)Smoke Testing should be done. 6)Smoke Testing should be done. 6)Smoke Testing should be done. 5)Resources should be available.
5)Resources should be available. 6)Smoke Testing should be done. 5)Resources should be available. 6)Smoke Testing should be done. do smoke testing to check whether files are the end, if you have some time you can do 7)Functional,Integration, System testing should 7)Functional,Integration, System testing should be 7)Functional,Integration, System testing should be 6)Smoke Testing should be done.
6)Smoke Testing should be done. 7)Functional testing should be done. 6)When minimum bunch of modules are 7)Functional,Integration, System, copied properly and build/sw is insalled Adhoc testing. Suppose if you don’t have time be done. done. done. 7)Functional,Integration, System testing
7)Functional test Scenarios and Test 8)Integration test Scenarios and Test ready 7)Smoke Testing should be done. Usability,Realibility, Recovery, Global, Performance properly or not. document the adhoc scenarios and communicate 8)Usability test Scenarios and Test cases 8)Performance test Scenarios and Test cases should be 8)If the software is developed for different should be done.
cases should be ready. cases should be ready. 8)Functional testing should be done. testing should be done. 3)Release Engineer /Build engineer will do to the TL should be ready. ready. langauges 8)If the software is developed for country
9)Integration testing should be done 8)Once after the SW quality is found good afetr smoke testingto check whether Build/ sw is 3).Once after complete SW is testd as per the standards / country culture
10)Testing server similar to production testing for number of cycles. installled properly into testing servers and requirement then we can do Adhoc testing (-ve
server setup should be available. production server. FT / IT / ST)
When 11)When we start getting less number of 4)Developer will do Smoke Testing after 4).Once after SW is tested for 10-15 days test
requirement doing WBT before giving build /sw to Test cycles and if the product / SW is stable then we
12)Basic functionalities of all the Engineer. will start doing adhoc testing (-ve FT / IT / ST)
modules should be working fine 5).While doing FT / IT / ST if you come up
13)Product/SW should be relatively with good adhoc scenarios stop doing FT / IT /
stable / no blocker / Critical defect ST and test for adhoc scenarios (-ve FT / IT /
14)System test Scenarios and Test ST) but dont spend too much of time in doing
cases should be ready. adhoc testing immediately switch back to FT /
IT / ST

To check if each and every line of To check whether each and every To check whether the data flow between To check when we navigate through all 1.To get confidence on the 1.To check that whether s/w 1.Chances are there customers or end users If we do exploratory testing when theres no To check weather SW or application is user To check, how is the response time and stability of an 1.To check wheather right language is displayed 1.To check wheather right date format is 1.TE will have tested the SW in
code is working as expected or not individual component is working as per one or more modules is working as per the features & check whether if the end product/software. or build is testable or not. use the SW randomly and they might find requirement we can find all blocker & critical friendly. application when load is applied. 2.To check weather right content is displayed in displayed one platform, chances are there the
the customer requirement specification. the customer requirement specification. featutre is working as expected or not. 2.To ensure that product meets the business 2.First day itself while doing smoke testing defects in order to avoid that sdhoc testing defectrs and we might miss some minor defects right place 2.To check wheather right currency format Users will use the SW in different
requirement if you find any defect, communicate to should be done. and when software is released to the customer. Our i.e, Easy to understand, simple language, easy to is displayed platforms & the SW might not
3.To make sure that s/w company is not developing develop. So, that developer will get sufficient 2.Develover & Te will look into the req and customer can use the SW and run the businesss access, easy to navigate, look and feel of the 3.To check wheather right Postal code is work. Whis will spread bad name
wrong feature. time to fix the defect. develop & test the SW, chances of finding the without facing any blocker problems. So when application should be good. displayed & customer usage will go down, In
4.Chances are there because of business pressure 3.We are doing smoke testing indirectly. we defects are less in thsi case, so TE will come up there is no requirement it is always best to do ET 4.To check wheather right image format is order to avoid this we should do
company might miss some defects. are ensuring build is insalled properly or not. with creative scenarios to find more defects. instead of releasing the SW to the customer displayed (National flag color) Compatibility testing
4.Developer is giving new build means he 3.This is negative testing, so adhoc testing has without testing 2.To ensure all the features is
Why will be doing some code changes and this to be doen. consistently working for all the
might affect old basic and critical features, In 4.Requirements are not followed, so we platforms we will do
order to find that we should do smoke testing. should adhoc testing. Compatibility testing
5.It is like health check up of the product, 5.The intention is to break the SW so we
so we should do smoke testing. should do adhoc testing. (Find max number of
6.Its like a build verification testing, we defects)
check whether
build is broken or not.

1.By writing flow chart Ex: MS Excel Ex: Gmail Ex: EPFO 1)Acc to the Case3(70%),Test engineers of company Ex: SBI.IN 1. I will understand the application and I will try to Ex: ESIC.GOV.IN Using performance testing tool (VU Gen) 1. Click 1.Right language 1.Currency format Ref : Diagram below Testing old or unchanged features to
2.By using 'true' & 'false' 1.To check that when user click on 1.When user select 3mails and click 1.When user enters URL:EPFO.GOV.IN travel to the Customers place and do Acceptance 1.To check that when user url welcome enter all possible inputs to each & every 1)Mobile number field is a mandatory field but on start recording 2.Right content in right place 2.Date format make sure that changes like adding a
condition in program bold, font should be be displayed in bold. on delete and click on trashes 3mails and welcome page should be displayed Testing,on demand of customers. page should be displayed. components and I will do ET there is no asterisk Symbol. 2.The recording will be started (it will capture each & 3.Alignment (Unidirectional / Bidirectonal) 3.Pin code format feature,removing a feature,modifying a
3.By usinging loop condition 2.To check that when user click on a should be displayed. and click on member passbook link and 2.To check that when user click signup, 2.I will understand the application & check data 2)when user enters todays date in DOF Text every actions we performs. 4.Tool tip 4.Image format feature and fixing defects is not
4.By using automation tool(if no. cell and click on copy the cell should be 2.When user click on compose send a login page should disply, enter UAN and signup page should be displayed. flow btw the module by doing ET field not diplying proper error message. 3.Open the browser, enter url, UN & Pwd and click on introdusing any defects by executing
How of lines of codes are more)5. highlighted with dotted line. mail to 2nd user and click on sent, Password and login home should be 3.To check that when user enter all valid 3. I wil explore the app & I will understand how 3)login button is enabled without entering any login button. same test cases of a feature when this
By improving data memory 3.To check that when user select two sended mail should be displayed. 3. displayed. data and click on signup, home page should every feature works and i will test all possible end data in any components. 4.click on stop recording. feature is new.
6. By improving performance of cells and click on merge and center,one When user click on compose a mail to be displayed. to end scenarios by doing exploratory testing. 5.The tool will automatically write the code for action,
codes cell should be displayed. 2nd user and click on back button, now enter the url and number of users into the tool and click
click on drafts mail should be
displayed.
1).Path tetsing( Cyclomatic 1).Over testing(Exhaustive Test) 1). Incremental Integration testing 1).End to End testing 1).User Acceptance testing(Productbase company) 1).Formal Smoke testing 1).Buddy testing - Dev & TE 1).Yellow Box testing 1).Load testing 1).Internationalization testing (I18N Testing) 1).Hardware compatibility 1).Unit Regression testing
Complexity) 2).Under testing a). Top down Incremental Integration 2).Acceptance tetsing 2).Operational Acceptance testing(Servicebase 2).Informal Smoke testing 2).Pair testing - TE & TE 2).GUI testing( Graphical User Inter Face) 2).Stress testing 2).Localization testing (L10N Testing) testing 2).Regional Regression testing
2).Conditional testing( Predicate 3).Optimize testing testing 3).Usability testing company) 3).Monkey testing - TE like monkey 3).Accesability Testing (American Disability 3).Scalability testing 2).Software compatibility testing 3). Full Regression Testing
test) a) +VE Testing b). Bottom up Incremental Integration 4).Performance testing 3).Contract Acceptance testing act)ADA 4).Volume testing
3.Loop testing b) -VE Testing testing 5).Compatibility testing 4). Compliance Acceptance testing 5.Soak testing(Endurance Testing)
Types 4).Unit testing 2).Non incremental Integration 6).Adhoc testing 5). Beta testing
5).Testing from memory point of testing(Bigg bang theory) 7).Regression testing
view 8) Smoke testing
6.Testing from performance point of
view
1.Open box tetsing * Hot Fix(Incident or Defect Management) 1).Sanity Testing 1).Monkey Testing 1).Baseline testing Localization testing (L10N Testing)- Portability Testing Release Candidate Testing
2.Glass box testing * Short release(Interrim release) 2). Dryrun Testing 2). GorillaTesting 2).Break point testing (Format testing)
3.Clear Box testing 3). Skim Testing 3). Out of the box Testing 3).Spike testing
Alternative 4.Transparent testing 4). Build vearification Testing 4). Negative Testing 4).Bottle neck testing
Component Testing
names 5.Mutation testing 5). Health check of a product Testing 5.Threshold testing
6.Structural testing 6). Confident Testing
7.Unit Testing 7). Positive Testing

Compatibility testing Compatibility testing

RAMESH.R.K