9) Usability testing: ➢ Usability means user friendliness.

The test engineer has to provide usability to

the application for the end user satisfaction. ➢ Depends on the application we have to provide the
usability. Ex: For Banking (secured) application we have to provide more security whereas for social
sites (Face book, twitter), we need to provide more user friendliness. 10) Adhoc Testing: ➢ Adhoc
means in our own way. ➢ Adhoc testing means test the application in your own way, After
understanding all the requirements and at least one round of manual testing is completed on the
application ➢ The main purpose of adhoc testing is to provide usability to the application. 11)
Exploratory Testing: ➢ Exploratory means identifying the new requirement / new Feature. Once the
build is stable the domain experts will test the application as per their domain knowledge, while
testing they will explore if the existing requirements are sufficient, if not they will provide the new
requirements. ➢ The main purpose of exploratory testing is to provide usability and security to the
application. 12) Monkey testing/Gorilla testing: ➢ Once the application is stable then we can go for
monkey testing. ➢ Perform testing on the application by doing some abnormal actions is known as
Monkey/Gorilla testing. ➢ Abnormal actions means continuously click on some field for long period
of time and check that whether the application is crashing or not. ➢ Test the application with invalid
data like HTML tags () and check that whether the application is crashing or not. Note: The objective
of monkey testing is to check whether the application is crashing or not (Means will get server not
found exception) 13) Static testing: ➢ Testing the application without performing any action is
known as static testing. Ex: GUI testing and checking the availability of the fields in the page
(Validations) comes under static testing. 14) Dynamic Testing: ➢ Test the application by performing
some action is known as dynamic testing. Ex: Regression testing, Retesting, Adhoc testing etc… 15)
Authentication testing: ➢ Authentication means check whether the secured credentials/data is
available in the database or not. ➢ Authentication testing means test the application with multiple
sets of valid and invalid data, for valid data it should display the homepage, whereas for invalid it
should display the proper authentication message (error message). Ex: Test the login functionality of
HMS with multiple sets of valid and invalid credentials. It has to authenticate the application
properly. 16) Direct URL testing: ➢ Login into a secure page and take the URL of the secured page
and access that URL in a new browser. Where it should not be accessible if it is accessible then the
application is not secured. Ex: Login into Gmail.com, copy the URL of the home page. Open in new
browser and access the URL directly, where it should not be accessible. 17) Firewall Leakage Testing:
➢ Login into the application as one level of user and try to access the data beyond your role
limitation. If it is accessible then we conclude that the application is not working as per the role (It is
having the firewall leakage). Ex: Login into the HMS application as Jr. Doctor and try to access the
data of Sr. Doctor, where it should not be accessible 18) Database Testing: ➢ Test whether the data is
properly inserting into the database of all the tables or not is known as database testing. With the
help of SQL queries we can perform DB testing. Ex: Whenever we are creating the permanent
registration in HMS, all the patient details will be stored in HMS database, as a test engineer we have
to login into the database and check that whether the data is properly inserted in all the tables or
not. Deployment Testing/ Installation Testing: The deployment team or Test lead will deploy the build
in multiple environments like dev, testing, stage1,stage2, production etc and check that whether its
properly deploying or not Q: Once the build is released, how you will test the build A: Initially we will
perform sanity testing, if it is pass then we will execute all the test cases then will perform all the
functional testing types as below. By performing all the below testing then we can ensure for quality
for the application Functional Testing types – Function testing’s execution flow on the Build, once its
released to testing team Note: For any web application all the above testing's will be performed to
ensure quality. If it is a desktop top application Direct URL Testing and cross browser testing is not
possible to perform. Review Report Template: Review the SRS document of spice jet and provide the
review report in the below template. Requirement ID Requirement Comments by TE Comments
Description 7. Adult, child and infant drop 1. What is the difference between Downs should be
available. Child, adult and infant 2. What values the adult, child, infant fields? 19) Globalization
testing: It is two of types a. Localization testing. b. Internationalization testing. a. Localization testing:
• Test the application in all the local languages which are selective to our country like Hindi, Bengali,
Telugu, etc. is known as localization testing. • It supports maximum of 10 languages for single
integration. Hence we will call it as ‘L10N’ testing. Ex: 1. Test Google.co.in in all the local languages
like Hindi, Bengali, Telugu etc… 2. Test the ATM machine in local languages likes Hindi, Telugu and
English. b. Internationalization testing: • Test the application in all the international languages like
Japanese, Chinese and Spanish etc. is known as internationalization testing. It supports maximum of
18 languages for a single integration. Hence we will call it as ‘I18N’ testing. Ex: Test Gmail.com in all
the international languages like, Japanese, Spanish and Chinese etc… SOFTWARE TESTING LIFE CYCLE:
It contains the below phases: 1) Software test plan. 2) Software test design. 3) Test Execution. 4)
Result analysis. 5) Reporting & BLC. 6) Delivery and maintenance. 7) Test summary report/ Build
postmortem report. 1. Software test plan: ➢ Plan is a strategic document which describes how to
perform a task in an effective and efficient way. ➢ Software test plan is also a strategic document
which describes how to perform testing in an effective and efficient way. The test plan will be
prepared by the test lead; once it is prepared it will be send to the testing team for review. ➢ Based
on the test plan we are responsible to perform testing. ➢ It contains below activities or Index. Test
plan Index 1. Objective 1.1 Scope of testing 2. Reference documents 3. Test Items 3.1 Features to be
tested 3.2 Features not to be tested 4. Test strategy 4.1 Testing types 4.1.1 Functional testing types 5.
Test environment 6. Test pass/Fail criteria 7. Defect analysis and closure 8. Test Deliverables 9.
Automation testing 10. Risks and contingencies 11. Hardware and software requirements 12.
Resource plan 13. Test summary report/ Build postmortem repor