Basic Software Testing interview Questions

41. If a project is long term project, requirements are also changes then test plan will change or not? Why?

• Yes. Definitely. If requirement changes, the design documents, specifications (for that particular module which implements the requirements) will also change. Hence the test plan would also need to be updated. This is because “Resource Allocation” is one section in the test Plan. 
• We would need to write new test cases, review, and execute it. Hence resource allocation would have to be done accordingly. As a result the Test plan would change

42. Explain VSS (Virtual Source Safe)?

• After completion of all phages from development side developer store the code in development folder of VSS, Testing team copying code from that folder to testing folder, after completing above phages from testing, testers put the build in base line folder. 
• It is version control Tool Mainly useful to developer, to storing code and maintains version Copying a code from VSS By developer is called CHECK-IN Upload the code in to VSS is called CHECK-OUT.

43. Who will assign severity & priority?

• The tester/developer should give the priority based on severity of the bug.
• Severity means: is the impact of the bug on the application .i.e seriousness of the bug interims of the functionality.
• Priority means: is how soon it should get fixed i.e. importance of the bug interims of customer

44. What is the Difference between Stub Testing and Driver Testing? 

• Stub testing:

In top down approach, a core module is developed. To test that core module, small dummy modules r used. So stubs r small dummy modules that test the core module. 

•  Driver testing:

In bottom up approach, small modules r developed. To test them a dummy core module called driver is developed.

45. What is a “Good Tester”?
 

• Is one who tries to break the developers software and in a position to venture the bugs. So that at least 80% bugs free software can deliver.

46. What is cookie And Session testing?
 

• A small text file of information that certain Web sites attach to a user’s hard drive while the user is browsing the Web site. 
• A Cookie can contain information such as user ID, user preferences, archive shopping cart information, etc. Cookies can contain Personally Identifiable
• Information. Session is a connection between a server and client.

47. How would you perform testing manually for web site?

• By noting the time to load page or perform any action with stop watch. I know it sounds funny but this is the way performance is tested manualy.

48. What is use case? Tell me the attribute of use case?

“Use Case is description of functionality certain features of an application interims of Actors, actions and responsibilities.”

Use Case attributes are:

1. Information of Document 
2. Description
3. Objective
4. Actors
5. Pre-conditions
6. Data-element descriptions
7. post conditions
8. primary flow
9. Alternative flow and Business rules/interaction implementations and etc….

49. What is the difference between stress, volume and load testing?

• Load Testing gradually increase the load and check the performance of the application .v check at what point or maximum load application can sustain.
• Stress testing: In this testing v check the performance of application under extreme condign which rarely occurs like

1. Many concurrent user access the application for short time.
2. Extra ordinary long transaction.
3. Very short transaction reputed quickly. 

50. When will do the beta test? When will do the alpha test?

• Alpha and Beta tests comes under User acceptance test. We will conduct these two systems being released. We are giving opportunity to customer to check all punctualities covered or not.
• Alpha testing conducting for software application by real customer at development site.
• Beta testing conducting for software product by model customer at customer site.

52. How do you select test cases for Regression Testing (The point is when there is change code how do you come to know which part of code or modules it will affect)?
 

• Consider an example of a form which has a user name, password and Login button.
  There is a code change and a new button “Reset” is introduced. Regression testing (for that build) will include testing only the “Login” button and not the Reset button (testing Reset button will be a part of conation testing). Hence the Regression tester need not worry about the change in code, functionality. But he has to make sure that the existing functionality is working as desired. Testing of “Reset” button will be included as a part of Regression, for the next build

53. Can you explain with example of high seviority and low priority, low seviority and high priority, high seviority and high priority, low seviority and low priority?
 
    1.High severity and high priority - Database connectivity cannot be established by     multiple users.    2. Low severity and low priority - Small issues like, incorrect number of decimal digits in         the output.    3. Low severity and high priority - Images not updated.    4. High severity and low priority - In a module of say 2 interfaces, the link between them is     broken or is not functioning.

    (1). High priority & High Severity: If u clicks on explorer icon or any other icon then system crash.    (2). Low priority & low severity: In login window, spell of ok button is “Ko”.    (3). Low priority & high serverty: In login window, there is a restriction login name should be 8 characters if user enter 9 or than 9 in that case system get crash.    (4)High priority & low severity: Suppose logo of any brand company is not proper in their     product. So it affects their business.

54. What will be the Test case for ATM Machine & Coffee Machine?
 
Test cases for ATM Machine1. Successful inspection of ATM card
2. Un successful operation due to insert card in wrong angle
3. Un successful operation due to invalid account ex: other bank card or time expired card
4. Successful entry of PIN number
5. Un successful operation due to enter wrong PIN number 3times
6. Successful selection of language
7. Successful selection of account type
8. Un successful operation due to invalid account type
10. Successful selection of withdraw operation
11. Successful selection of amount to be withdraw
12. Successful withdraw operation
13. Unsuccessful withdraw operation due to wrong denominations
14. Unsuccessful withdraw operation due to amount is greater than day limit
15. Unsuccessful withdraw operation due to lack of money in ATM
16. Unsuccessful withdraw operation due to amount is greater than possible balance
17. Unsuccessful withdraw operation due to transactions is greater than day limit
18. Unsuccessful withdraw operation due to click cancel after insert card
19. Unsuccessful withdraw operation due to click cancel after insert card & pin number
20. Unsuccessful withdraw operation due to click cancel after insert card, pin number & language
21. Unsuccessful withdraw operation due to click cancel after insert card, pin number, language &account type
22. Unsuccessful withdraw operation due to click cancel after insert card , pin number , language ,account type & withdraw operation
23.unsuccessful withdraw operation due to click cancel after insert card , pin number , language ,account type ,withdraw operation &amount to be withdraw

55. Tell me about your daily activities as a test engineer?
 
Role:
1. Understanding the BRS and Use cases Document
2. Giving system demo to PM, System analyst, designer, Dev lead.
3. Preparing the Test Actions in xls sheet.
4. Updating the Test Actions based on review comments by System analyst/Business Analyst.
5. Preparing the Test cases and Datasets (System level and global level datasets) in word document
6. Updating the Test Cases based on review comments by System analyst.
7. Installing the application-Testing environment set up.
8. Performing Functional, GUI, System, Compatibility testing (If necessary), Regression testing based on Test cases
9. Preparing the defect report, Bug tracking list and sending daily status report to PM, leads.

56. In SDLC process what is the role of PM, TL, DEVELOPER, tester in each and every phase? Please explain me in detail?
 
In the SDLC we have these phases
1. Initial phase
2. Analysis phase
3. Designing phase
4. Coding phase
5. Testing
6. Delivery and maintenance

• In the initial phase project manager can prepare a document for the requirements, team leader will prepare a team which is having test engineers, developer will provided by the project manager, tested will prepare test cases for that particular project
• Analysis phase all the members have a meeting to finalize the technology to develop that project, the employee, time…
• Designing phase the project manager like senior level management will give the directions and source code to the team members to develop the actual code that is guidelines will be given in this phase
• Coding phase developer will develop the actual code using the source code and they release the application to the tested
• Testing phase they deploy their test cases to that application and prepare a bug profile document if there is any defect/bug in that application and send it back to developer, developer may rectify and releases than application as next build and if the bug not understand it will send to the project lead in the delivery phase the so test eng can deploy the application in the client environment
• Maintenance phase if the client get any problem with the application it may solved by the project lead with help of testers and developers

57. How do you Test Application with having any requirement and Document?

• If it is an existing system or if a build is available then we explore the system while testing. This helps knowing the functional use of the system, and its usability.
• By asking questions to end users and how they use it will be more beneficial. Also, you may work with BA to know more about the system.
• Black box test is nothing but the same where you explore the system without having any prior knowledge to the system.

58. What is back end testing using SQL?

• Executing SQL statements to check if the data submitted by a GUI program is updated in the database or not? Executing the statement the data base is connecting to that particular changes, updations or not it will test. Back end testing is the testing the integration between the application and the database. It is checking the changes made in the database are getting reflected in the application.
• Example: A new column is added in the table. Here we test by giving values in the application and value has to be stored in the table.

59. What are the reasons why parameterization is necessary when load testing the Web server and the database server?

• When you test your applications, you may want to check how the application performs the same operations with multiple sets of data. For example, suppose you want to check how
• Your Web site responds to ten separate sets of data. You could record ten separate tests, each with its own set of data. Alternatively, you can create Data Table parameters so that your test runs ten times, each time using a different set of data.

60. Difference between strategic test plan & test plan?

• Strategic test is an organizational level term which is applied for all the projects in the organization with small customizations
• Test plan is project level term and which can be applied for that specific project only.
• Test plan is a strategic document which describes how to perform testing in an efficient effective and uptimes way. Quality lead test lead can prepare this test plan
• Strategic test plan is an already or new test plan which can bow used in the future for another project also with some changes in the same organisation.

Manual Software Testing interview Questions

21. What are the client side scripting languages and server side scripting languages?

1.  Client side scripting languages

•  Javascript, VbScript, PHP…etc

• Server side Scripting languages are

• Perl, JSP, ASP, PHP.etc

• Client side scripting languages are useful to validate the inputs or user actions from user side or client side.

     2.Server side Scripting languages

• Server side Scripting languages are to validate the inputs at server side.

•  These scripting languages provide security for the application and also provides dynamic nature to web or client server application

• Client side scripting is good because it won’t send the unwanted input’s to server for validation. 
• From front-end it self it validated the user inputs and restricts the user activities and guides him.

22. If a very low defect (user interface) is detected by u and the developer not compromising with that defect,what will u do?
 
User interface defect is a high visibility defect and easy to reproduce.
Follow the below procedure
    1. Reproduce the defect
    2. Capture the defect screen shots
    3. Document the proper inputs that you are used to get the defect in the defect report
    4. Send the defect report with screen shots, inputs and procedure for defect reproduction.
    5.Before going to this you must check your computer hard ware configuration that is same as developer system configuration. and also check the system graphic drivers are properly Installed or not. If the problem in graphic drivers the User interfaces error will come.
So first check your side if it is correct from your side then reports the defect by following the above method.

23.if u r only person in the office and client asked u for some changes and u didn’t get what the client asked for what will u do?
 

• One thing here is very important. Nobody will ask test engineer to change software that is not your duty, even if it is related to testing and anybody is not there try to listen care fully if you are not understand ask him again and inform to the corresponding people immediately.

• Here the client need speedy service, we (our company) should not get any blame from customer side.

24. How to get top two salaries from employee tables?

• Select * from EMP e where 2>= (select count (*) from EMP e where sal>e.sal) order by desc sal.

25. How many Test-Cases can be written for the calculator having 0-9 buttons, Add, Equalto buttons? The test cases should be focused only on add-functionality but mot GUI.What is those test-cases?
 
Test-Cases for the calculator

• so here we have 12 buttons totalize 0,1,2,3,4,5,6,7,8,9,ADD,Equalto -12 buttons
• here u can press at least 4 buttons at a time minimum for example 0+1= for zero u should press ‘zero’ labeled button for plus u should press ‘+’ labeled button for one u should press ‘one’ labeled button for equal to u should press ‘equal to’ labeled button 0+1=here + and = positions will not vary so first number position can be varied from 0 to 9 i.e. from permutation and combinations u can fill that space in 10 ways in the same way second number position can be varied from 0 to 9 i.e. from permutation and combinations u can fill that space in 10 ways
• Total number of possibilities are =10×10=100
• This is exhaustive testing methodology and this is not possible in all cases.
• In mathematics we have one policy that the function satisfies the starting and ending values of a range then it can satisfy for entire range of values from starting to ending.
• then we check the starting conditions i.e. one test case for ‘0+0=’ (expected values you know that’s ‘0′) then another test case for ‘9+9=’(expected values you know that’s ‘18′) only two test cases are enough to test the calculator functionality.

26. What is positive and negative testing.Explain with example?

• Positive Testing - testing the system by giving the valid data.
• Negative Testing - testing the system by giving the Invalid data.
• For Exam application contains a textbox and as per the user’s Requirements the textbox should accept only Strings. By providing only String as input data to the textbox & to check whether its working properly or not means it is Positive Testing. If giving the input other than String means it is negative Testing.

27. How will you prepare Test plan. What are the techniques involved in preparing the Test plan?

• Test plan means planning for the release. This includes Project background
• Test Objectives: Brief overview and description of the document
• Test Scope: setting the boundaries
• Features being tested (Functionalities)
• Hardware requirements
• Software requirements
• Entrance Criteria (When to start testing):
• Test environment established, Builder received from developer, Test case prepared and reviewed.
• Exit criteria (when to stop testing):
• All bug status cycle are closed, all functionalities are tested, and all high and medium bugs are resolved.
• Project milestones: dead lines

28. What is the Defect Life Cycle?
 
Defect life cycle is also called as bug life cycle. It has 6stages namely    1. New: found new bug
    2. Assigned: bud assigned to developer
    3. Open: developer is fixing the bug
    4. Fixed: developer has fixed the bug
    5. Retest: tester retests the application
    6. closed/reopened: if it is ok tester gives closed statuselse he reopens and sends back to developer.

29. Expalin about metrics Management?
 

• Metrics: is nothing but a measurement analysis.Measurment analysis and Improvement is one of the process area in CMM I L2.

30. What is performance Testing and Regression Testing?
 

• Performance Testing:-testing the present working condition of the product.

• Regression Testing:-Regression Testing is checking for the newly added functionality causing any errors interims of functionality and the common functionality should be stable In the latest and the previous versions

31.How do you review test case? Type of Review…
 

• Types of reviewing test cases depend upon company standards, viz..,

• Peer review, team lead review, project manager review.

• Some times client may also review the test cases reg what is approach following for project

32. In which way tester get Build A, Build B, Build Z of an application, just explains the process?

• After preparation of test cases project manager will release software release note in that Document there will be URL path of the website link from that we will receive
• The build In case of web server projects, you will be provided with an URL or a 92.168. ***. *** (Web address) which will help you access the project using a browser from your system.
• In case of Client server, the build is placed in the VSS (Configuration tool) which will help you get the .exe downloaded to your computer.

33. Apart from bug reporting what is your involvement in project life cycle?

• As a Test engineer we design test cases, prepare test cases Execute Test cases, track the bugs, analyze the results report the bugs. Involved in regression testing, performance of system
• Testing system integration testing at last preparation of Test summary Report

34.What are the contents of test report?
 
There are two documents, which should be prepared at particular phase.

1. Test Results document.
2. Test Report document.

• Test Results doc will be prepared at the phase of each type of Testing like FULL FUNCTIONAL TEST PASS,REGRESSION TEST PASS,SANITY TEST PASS etc…Test case execution against
• The application. Once you prepared this doc, we will send the doc to our TL and PM.By seeing the Test Results doc, TL will come to know the coverage part of the testcase.Here I am giving you the contents used in the Test Results doc?

1. Build No
2. Version Name
3. Client OS
4. Feature set
5. Main Feature
6. Defined Test cases on each feature.
7. QA engineer Name
8. Test e-cases executed. (Includes pass and fail)
9. Testcases on HOLD (Includes blocking test cases and deferred Test cases)
10. Covereage Report (Which includes the coverage ratings in %, like % of test cases covered, % of test cases failed)

Coming to Test report, generally we will prepare Test report, once we rolled out the product to our client. This document will be prepared by TL and delivered to the client.Mainly, this document describes the what we have done in the project, chievements we have reached, our Learning’s in throughout the project etc…The other name for Test report is Project Closure Report and we will summarize the all the activities, which have taken place in through out the project. Here I am giving your the contents covered in the Test Report.

    1. Test Environment (Should be covered the OS, Application or webservers, Mahchine names, Database, etc…)    2.Test Methods(Types of Tests, we have done in the project like Functional Testing, Platform Testing, regression Testing,etc..    3. Major areas Covered.
    4. Bug Tracking Details. (Includes inflow and outflow of the bus in our delivered project)
    5. Work schedule (When we start the testing and we finished)    6. Defect Analysis        6.1 Defects logged in different types of tests like Functional Test, regressiion Test as per area wised.        6.2 State of the Defects at end of the Test cycle.        6.3 Root cause analysis for the bugs marked as NOT A BUG.    7. QA observations or learning’s thought the life cycle.

35. Write high level test cases?

• Write all the test cases under high level TC, which can be covered the main functionalities like
• Creation, edition, deletion, etc….as per prescribed in the screen.
• Write all the test cases under low level TC,which can be covered the screen, like input fields are displayed as per the requirements, buttons are enabled or disabled, and test case for low priority functionalities.
• Example a screen contains two edit boxes login and password and a put buttons OK and Reset and check box for the label “Remember my password”. Now let us write high level TC
• And low level test cases.

HIGH LEVEL TESTCASES

    1. Verify that User is able to login with valid login and valid password.    2. Verify that User is not able to login with invalid login and valid password    3. Verify that Reset button clears the filled screen.    4. Verify that a pop up message is displayed for blank login.

LOW LEVEL TC    1. Verify that after launching the URL of the application below fields are displays in the screen.    2. Login Name 2.Password.3.OK BUTTON 4.RESET button etc.    3. Check box, provided for the label “remember my pwd” is unchecked.    4. Verify that OK button should be disabled before selecting login and password fields.    5. Verify that OK button should we enabled after selecting login and password.    6. Verify that User is able to check the check box, providedfor the label “remember my password”.
In this way, we can categories all the test cases under HIGH LEVEL and LOW LEVEL.

36. What is test scenario?
 

• Test scenario will be framed on basis of the requirement, which need to be checked. For that, we will frame set of test cases, in other terms, we can say all the conditions, which can be determined the testing coverage against business requirement.
• Please see the below example, which is exactly matched to my explanation.
• As we know all most all the application are having login screen, which contains login name and password. Here is the test scenario for login screen.

Scenario: USER’S LOGIN

Conditions to be checked to test the above scenario:
—————————————————-
1. Test login field and Password fields individually.
2. Try to login with valid login and valid password.
3. Try to login with invalid login and valid password. Etc

37. What is build duration?
 

• it is a tine gap between old version build and new version build in new version build some new extra features are added

38. What is test deliverables?

• Test deliverables are nothing but documents preparing after testing like test plan document test case template bug report template Test deliverables will be delivered to the client not only for the completed activities, but also for the activites, which we are implementing for the better productivity. (As per the company’s standards).Here I am giving you some of the Test deliverables in my project.

    1. QA Test Plan    2. Test case Docs    3. QA Test plan, if we are using Automation.    4. Automation scripts    5. QA Coverage Matrix and defect matrix.    6. Traceability Matrix    7. Test Results doc    8. QA Schedule doc (describes the deadlines)    9. Test Report or Project Closure Report. (Prepared once we rolled out the project to client)    10. Weekly status report (sent by PM to the client)    11. Release Notes.

39. What is your involvement in test plan?

• Test lead is involved in preparing test plan test engineers are no way related in preparing test plan role TE is test case design, and execution and bug tracking and reporting them Generally TL is involved in preparation of the TestPlan.But it is not mandatory only TL will take main part in the preparation of the TP.Test engineer can suggest to TL, if he (or) she has good understanding on project and resources, if he or she has more exp with the project, if TL is wrongly given deadlines. If your suggestions are valid, TL will incorporate all of them to the TestPlan.But in most of the companies Test engineers are just audience.

40. Which test cases are not to be automated?
 

• All the test cases which are related to a feature of the product, that keeps on changing (there are always some or the other enhancements in it). Frequent enhancements may change the UI, add/remove few controls. Hence such cases, if automated, would involve lot of a intendance

Freelance Software testing jobs - Earn From Home without investment

Best Companies That Pay You To Test Websites from Home.

 

 What Software Tester Need to Do?

• Test Random website Look and Feel
• Website Navigation
• Tell Some Suggestion about website Design 

Basic requirements

Updated PC or Laptop

High-speed Internet

Mobile Device (Android/iPhone) - for Application Testing

Companies list which provide Freelance Software Testing

• UserTesting
• Whatusersdo
• UserTest 
• Enroll 
• UTest 
• UserFeel
• Start Up Lift 
• Analysia
• TryMyUI
• Userlytics .
• Amazon Mechanical Turk
• Testing Time 

Manual Testing Vs. Automation Testing

There are various ways of software testing. Manual testing is the methodology of humans doing all the testing. For a long time this worked very well. But today there is so much preponderance of software that it is just not feasible for humans to test all the software manually. This is where the software testing automation takes over. 

There are a lot of advantages of automated testing process thanks to its adherence to speed and accuracy which humans are just not able to achieve but 100% Manual testing can’t Replaced with Automation testing because both Testing is best suited for different type of testing.

First Understand difference between both Testing and also advantage and disadvantages of both Testings.

Criteria	Manual Testing	Automated Testing
Basic premise	Less accurate and cannot perform repeated tasks	Highly reliable for repeated tasks as it uses tools and scripts
Time taken	Needs lots of time	Is a very fast process
Investment	Needed for human resource	Needed for the software tools
Generally used when	Test cases are run once or twice	Test cases are run repeatedly
For User Interface Testing	Highly effective since it involves human intervention	Not effective since there is no human intervention
Initial cost	Very less	It is high
For Build Verification Testing	Not recommended	Highly recommended

At the end of the day the type of testing that you need is totally dictated by the requirement of the project, the kind of budget that is available and what is the testing methodology that will benefit the given deadlines, customer expectations and so on.

When it comes to exploratory, usability and ad-hoc testing the best way to test the cases is through manual testing. When it comes to performance testing, load testing, regression testing, and repeated testing we can rest assured that automated testing is the best one.

There are many testing types which are carried out manually as well as automatically. There is blackbox and whitebox testing. The blackbox testing is more about the system settings, the configuration and other aspects without looking into the internal working of the software. The whitebox testing is the one which tests the logic, algorithm, and internal working of the software like branches, paths, code statements and conditions.

In the integration testing we will be having the testing of the various joint functionalities after integration, code modules and the various applications like client, server, individual and so on. This type of integrated testing is most suitable for the distributed systems and the client server applications.

Manual testing is best suited for:

Exploratory Testing : in this type of testing the knowledge and experience of the tester along with his analytical and logical mindset is of utmost importance. It needs in equal measure the creativity and intuition. This type of tests has documentation that is poorly written. So the tester has to ensure that the execution of the process is completed.

Usability Testing :This is the testing wherein you will find out how user-friendly the certain software product is. So for this the human observation is crucial without which the usability test cannot pass muster.

Ad-hoc Testing :The very name of the test implies that it is done on an ad-hoc basis to serve some specific purpose. So this can only be done by the humans and since there is no set plan, the machines are not able to do it.

Automated Testing is best suited for :

Regression Testing : this type of testing is best suited for the automated testing as there are frequent code changes and it is beyond the human capacity to run the test in a timely manner and this is the right type of testing for automation.

Load Testing :  For load testing applications the automation testing is the right type of testing.

Repeated Execution – when it comes to repeated execution we can deploy automation testing.

Performance Testing – The process of performance testing includes simulating the hundreds of concurrent users and it is best suited for automation testing.

Then there are other types of testing which as per the situation, project, organization and the need can be done either by manual testing methodology or automated testing methodology.

The tests which can be done through automated or manual approach:

Integration Testing – Integrated modules testing method to verify joint functionality after integration. Modules are typically code modules, individual applications, client and server applications on a network, etc. This type of testing is especially applicable to client/server and distributed systems.

System Testing – It tests the entire system for any errors or bugs in the system.

Unit Testing – In this type of testing we can see that the software components and modules are tested and this needs the thorough knowledge of the various internal programming of the code and design.

Acceptance Testing – In the acceptance testing we can see that the system meets the various customer requirements. It is normally done by the customer before accepting any software application to verify its efficacy.

Now that you know the various scenarios in which each of the software testing methodologies are used, it is up to you and your organization to choose one over the other. It is all about taking the right decision to ensure that the software when delivered to the client is of the highest quality.