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.