Explore topic-wise InterviewSolutions in .

Top 53 Sotware Testing tools
Below are the list of 50 most popular testing tools
(1)qTest
(2)Testpad
(3)Practitest
(4)Zephyr
(5)QMetry
(6)TestRail
(7)Test Collab
(8)QAComplete
(9)TestLink
(10)Squish
(11)Ranorex
(12)Selenium
(13)QTP
(14)Watir
(15)Testim
(16)AppliTools
(17)Telerik
(18)TestComplete
(19)Webload
(20)Loadrunner
(21)Wapt
(22)LoadUI Pro
(23)SILK Performer
(24)Jmeter
(25)AileLoad
(26)LoadFocus
(27)BlazeMeter
(28)LoadImpact
(29)JIRA
(30)Mantishub
(31)FogBugz
(32)Bugzilla
(33)BugNet
(34)Bug Genie
(35)RedMine
(36)APPIUM
(37)Espresso
(38)PERFECTO
(39)ExperiTest
(40)Robotium
(41)Browsera
(42)CrossBrowser Testing
(43)SauceLabs
(44)Ghostlab
(45)Browsershots
(46)SoapUI
(47)SOAPSonarWeb
(48)WebInject
(49)Tricentis
(50)NetSparker
(51)OWASP
(52)Acunetix Vulnerability Scanner
(53)W3C CSS validator

Three test CASE which we take care while doing Unit Testing?
Below are the 3 test case which we doing while doing Unit Testing:
(1)POSITIVE Test case:-Here we will send correct data to application and expect the correct output.
(2)Negative Test Cases:-Here we will send some incorrect or invalid values and expect that there should be PROPER handling of that incorrect values.
(3)Exception Test Cases:-Here we will check all the exception are HANDLE correctly.

(1)Positive test cases (correct data, correct OUTPUT)
(2)negative test cases (BROKEN or missing data, PROPER handling)
(3)Exception test cases (exceptions are thrown and caught PROPERLY).

Write down FIVE MAIN difference between White Gray and Black Box testing
(1)Black box testing:-When we say about Black Box Testing we does not need the knowledge about how PROGRAM is implemented.
(1)Gray box testing:-In Gray Box testing we need limited knowledge of an internal program.
(1)White box testing:-In White Box Testing we need full implementation knowledge of program.

(2)Black box testing:-Black Box testing has very low granularity.
(2)Gray box testing:-Gray Box Testing has medium level of granularity
(2)White box testing:-White Box testing has very high level of granularity.

(3)Black box testing:-Other names of Black Box Testing are opaque box testing, closed box testing, input-output testing, data-driven testing, behavioral testing and functional testing.
(3)Gray box testing:-Gray Box Testing are also known as translucent testing.
(3)White box testing:-White Box Testing are also know as Glass Box Testing and Clear Box testing.

(4)Black box testing:-Black Box testing is a user acceptance testing and is done by end users.
(4)Gray box testing:-Gray Box Testing is also a user accpetance testing.
(4)White box testing:-White Box Testing is done by Testers and programmers.

(5)Black box testing:-In Black Box Testing TEST case are made by the functional specifications as internal details are not known.
(5)Gray box testing:-In Gray Box Testing test cases are made by the internal details of a program.
(5)White box testing:-In White Box testing test cases are made by the internal details of a program.

What do you understand by USE Case Testing
Use Case Testing Technique is mainly helps to identify test case that covers the ENTIRE TRANSACTION or we can say entire system with all transactions from start to finish. Or in other world we can say to KNOW the functional requirement of enitre application from start to finish we use case and this techniques is known as Use Case Testing. And this is mainly used to develope test or system for ACCEPTABLE levels.

1. Need to check if correct data is getting saved in database once submiting it
2. Need to check values for columns which not accept null value
3. Need to check data integrity where data should be saved in single or multiple tables asper the design
4. Index names should be given as per the standards e.g. IND_Tablename_ColumnName
5. Tables must have primary key column
6. Table columns should have description information AVAILABLE for some scenrio it is avoid for some column like for created date and created by etc.
7. There must be log For every database add and update operation
8. Must have the Required table indexes should be created
9. Need to check data is committed to database only when the operation is successfully completed
10. Must have applied commit and rollback function so that it will HELPS in case of failed transactions
11. Developer must takecare of Database name it should be given as per the application type i.e. test, UAT, live etc.(It is a good practice)
12. Database logical names should be given according to database name (It is a good practice)
13. Stored procedures should not be named with prefix SP becasue this is for system store procedure
14. Need to check values for table audit columns like updatedate, updatedby,createddate, createdby, isdeleted, deleteddate, deletedby etc. are filled properly
15. Need to check the input data is not truncated while saving.
16. Need to check numeric fields with minimum, maximum, and float values
17. Need to check numeric fields with negative values in both acceptance and non-acceptance
18. Need to Check if radio button and dropdown list options are saved correctly in database
19. Need to check the database fields are designed with correct data type and data LENGTH
20. Need to check if all table constraints like Primary key, Foreign key implemented correctly
21. Need to check the stored procedures and triggers with sample input data
22. Need to check input field leading and trailing spaces should be truncated before committing data to database
23. Need to check the null values should not be allowed for Primary key column
24. Need to check field length shown to user on page and in database schema should be same

What is Capacity Testing and its Types
Capacity testing is one of the most important or critical testing technicque. Here we will CHECK both LOAD and stress testing. Here we will verify the technical aspects that why answer is (b). Here we will check both the number of transaction as well as the number of USER that are working on the application.
Below are the 3 types of Capacity testing
(1)Load
(2)Stress
(3)Capacity

Five main points that COVERS in White Box testing of database
Below are the 5 main points covers when we doing white box testing of database
(1)First we will check the Database Consistency and ACID properties.
(2)Will also check Database TRIGGERS and the logical views.
(3)In third white box testing will also covers decision COVERAGE, condition coverage and the statement coverage
(4)This testing also includes database tables, data model and the database schema.
(5)Will also covers referential INTEGRITY rules.

Basic steps includes in Life Cycle of Bug
Below are the seven steps included in life cycle of Bug
(1)First step is once tester identified the Bug or Defect he will assigned that to

development manager in open status.
(2)Second step is to check is the defect or bug raised is valid or not if it is then

it will transfer to development team to fix it.
(3)Third step is to check if defect is not valid then it will be ignored or

rejected.
(4)Fourth step is to check whether it is in scope or not. If bug is not part of

current release then defect should be postponed.
(5)Fifth step is to check if defect or bug is allready raised then it will ASSIGN as duplicate status.
(6)SIXTH step is handle by the developer while they are busy in fiing the defect it will be given in in-progress status.
(7)And final step here is once the developer REPAIRED the status is changed to fixed and once tester will test then it will CHANG status to fixed it is passes in final test.

What do you mean by Boundary value testing?
Test boundary conditions means testing below and above the edges of input OUTPUT equivalence classes. For example we take a example of BANK application where some minimum and maximum limit is SET. LET say a bank application where you can withdraw maximum Rs.20,000 and a minimum of Rs.100, so in boundary value testing we test only the EXACT boundaries, rather than hitting in the middle. That means we test above the maximum limit and below the minimum limit.

Use CASE: It is prepared by Business analyst in the Functional Requirement Specification (FRS), which is nothing but steps which are given by the customer.

Test cases: It is prepared by test ENGINEER based on the use cases from FRS to CHECK the functionality of an application thoroughly.

Test Plan: Team LEAD prepares test plan, in it he represents the scope of the test, what to test and what not to test, scheduling, what to test using automation ETC.

What is SMoke and Sanity Testing and there difference
Both are the 2 most confused forms of testing which often used INTERCHANGEABLY. Below is defination followed by the difference.

(1)Smoke Testing:- To do hardware or electrical device testing practices when there is a new device was used to checked or operated to see if it doesnot smoke. In smoke testing is done to ensure that normal functionalities are working fine and ALSO check the release is stable enough to be tested.

(2)Sanity Testing:-In this testing technique we will test a particular functionality of software is verified for its correctness instead of performing regression on complete build. Sanity testing is subset of regression testing with the intend of saving time.

Now the diference between two of this is given below
(1)Smoke Testing:-It is a shallow and wide approach of testing
(2)Sanity Testing:-It is a narrow and deep approach of testing

(1)Smoke Testing:-Here build may be either stable or unstable
(2)Sanity Testing:-Here build is relatively stable

(1)Smoke Testing:-It is performed by both Developers and TESTERS
(2)Sanity Testing:-It is performed by Testers alone

(1)Smoke Testing:-These are TESTS are usually(preferably) automated
(2)Sanity Testing:-Sanity tests are generally not automated or even documented as test cases

(1)Smoke Testing:-To ensure that the build is good enough to be CONSIDERED for carrying on full-fledged testing
(2)Sanity Testing:-It is done to ensure that after a new fix the particular component is working fine

(1)Smoke Testing:-Smoke Testing exercises the entire application from end to end
(2)Sanity Testing:-Sanity Testing exercises only the particular component of the entire application

Below are the steps to test a printer:-
(1)Test for power supply
(2)Pc connection test
(3)Printer SAMPLE test
(4)BUFFER test
(5)Alignment test
(6)Test for clarity
(7)SPEED of printing
(8)Performance

As we all know software testing is an important aspects of software DEVELOPMENT process. Software development contains 4 main steps which is knows as PDCA(Plan,DO/Execute,Check/Test,Act). As above four steps contains A to Z of development.
Now i will explain every step ONE by one





(1)Plan: Here we will define the goal and then plan accordingly to achieve the same
(2)Do or Execute: After planning we will execute the step we define in planning
(3)Check: Here we will ensure whether we are moving in right direction or not.
(4)Act: If we get and issue or bug after the THIRD step we will take appropriate action on them in 4 act.

Here in above 4 point developer and other stakeholder do planning and BUILDING while tester do the check part. So PDCA also contains testing part as well.

What do you MEAN by traceability MATRIX?
Traceability matrix is ONE TYPE of DOCUMENT. This document is used to show the relationship and this relationship is in between test cases and requirements.