Month: September 2019

150+ Software Testing Interview Questions and Answers

Posted on by tbsupadminnxtbackendacc

In this post, we will share the kind of software testing interview questions asked in meetings with the employee to help individuals seeking to secure a software tester job profile.
1. Which Methodology do you follow in your Test Case?
 A. Phase Containment is consolidating QA into each of the stages of SDLC. It brings about Defect Prevention. In the event that QA group performs Design Review, Requirements Review, and Code Review, errors would be not many when a real application is tested. That implies we have averted numerous errors by performing reviews at each phase of SDLC.
2. What is Black box testing? What are the distinctive discovery Testing Strategies?
A. Black box testing is the product testing technique that is applied to test the product without distinguishing the internal structure of a program or code. This testing is typically done to validate the functionality of an application.
The various black box testing systems are:

  • Boundary value analysis
  • Equivalence Partitioning
  • Cause-effect graphing

3. What are Quality Control and Quality Assurance?
Quality Assurance includes in process-oriented practices. It guarantees the counteractive action of bugs in the process utilized to make software application. So, the bugs don’t emerge when the software application is being produced.
Quality Control includes product-oriented practices. It administers the code or program to distinguish the bugs in the software application.
4. How well do you deal with Ambiguity?
A.Test cases are not generally straightforward and QA Engineers should follow up on their own judgment. They have to feel great with ambiguity.
5. How well do you Function with others?
A. Several QA teams have colleagues who are from all edges of the world. QA engineers must be content with speaking with individuals at all levels and all backgrounds.
6. How might we perform Spike testing in JMeter?
A. JMeter accompanies a synchronizing timer which can deal with the demands of numerous threads. It can get the expected number of strings and discharge them immediately to cause a spike.
7. What is the chief contrast among st Reactive and Preventative strategies of Testing?
A. Reactive tests are planned after the product has been delivered and preventative tests are designed ahead.
8. What are the significant steps to fix issues while Testing?
Record – Log and handle any issues which have happened.
Report – Report the issues to high ranked manager.
Control – Define the issue management process.
9. What is the distinction between Test scripts, Test scenarios, and Test cases?
A.Test Scripts – They are composed in a programming language and it’s a short program used to test some portion of the functionality of the product framework. Simply speaking a written set of steps ought to be performed manually.
Test Scenarios – Test scenario is set up before the genuine testing begins, it incorporates plans for the testing software, environmental condition, number of colleagues, creating test cases, making test plans, and every one of the characteristics that are to be tested for the software.
Test cases – It is a record that contains the steps that must be performed, it has been planned before.

10. What are the classes of Defects?
A. Missing – There was a prerequisite given by the client and it was not done. This is a variance from the particulars, a sign that particular was not performed, or a necessity of the client was not recorded appropriately.
Wrong – The prerequisites have been performed wrongly. This defect is different from the given particular.
Extra – A prerequisite included in the software that was not given by the end-user. This is dependably a variance from the determination yet might be a trait wanted by the user of the software. But it is viewed as a defect due to its variance from the current prerequisite.
11. List out the Test Deliverables.
A.

  • Test Strategy
  • Test Plan
  • Test Cases
  • Test Scripts
  • Test Scenarios
  • Test Data
  • Effort Estimation Report
  • Requirement Traceability Matrix (RTM)
  • Test Execution Report
  • Defect Report/Bug Report
  • Test summary report
  • Test incident report
  • Test closure report
  • Test status report
  • Weekly status report to the Project manager and the client
  • Graphs and Metrics
  • Release Note
  • User guide
  • Configuration guide

12. What is Rapid Application Development?
A. Rapid Application Development (RAD) is formally a parallel development of functions and consequent integration. Functions are produced in parallel as though they were smaller than usual activities, the developments are time-boxed presented and after that congregated to a working prototype.
This can rapidly give the client an image to view and utilize and to give input with respect to the delivery and their prerequisites. Quick change and improvement of the software are probably applying this strategy.
In any case, the software particular should be created for the software sooner or later and the undertaking should be put under more formal controls before going into generation.
13. What’s the difference between Acceptance testing and System testing?
A. Acceptance testing checks the framework against the Prerequisites. It’s like System testing in which the entire framework is checked yet the vital contrast is the transition in focus.
System testing tests that the system that was indicated has been conveyed. Acceptance testing checks that the system will convey what was demanded. The client ought to dependably do Acceptance testing and not the engineer.
The client recognizes what is needed from the framework to accomplish value in the business and is the main individual equipped to make that determination.
This testing is more about guaranteeing that the product is produced as described by the client. It’s getting a green light from the client that the product meets requirements and is prepared to be utilized.
14. Clarify Random/Monkey Testing.
A. A strategy of software testing where the system is checked by randomly ingesting inputs. This test does not follow any pre-defined set of principles. It’s done to test the application behavior.
15. How to manage the low-frequency issues during the Testing?
A. By low frequency, I trust you mean the issues that can’t be replicated reliably after some time.
In case an issue isn’t coming up each time we repeat a similar series of steps, we do some drilling around to check whether we can discover any indication of the appearance of the bug (failure or logs messages), and when nothing else works, we report everything the same. As testers, we can’t leave anything without creating a report.
16. As a component of which test process do you decide the exit criteria?
A. The exit criteria are resolved on the basis of ‘Test Planning’.
17. What is Mutation testing?
A. This type of testing is used to detect if a set of the test case or test data is useful by intentionally presenting different code changes (bugs) and retesting with real test cases/data to decide whether the bugs are discovered.
18. While controlling your venture what things you need to acknowledge?
A. The things that must be taken in contemplations are:

  • Is your venture on the plan?
  • Are you working towards a similar career objective?
  • Have you got sufficient resources?
  • Are you overspending?
  • Are there any warning indications of approaching issues?
  • Is there any pressure from the administration to finish the undertaking quickly?

19. What is Unit Testing?
A. It is done to examine whether the individual module or unit of the source code is working legitimately. It is performed by the software developers in developer’s environment. Unit Testing is additionally known as Component Testing or Module Testing.
20. What is Alpha Testing and Beta Testing?
A. Alpha testing is finished by the in-house testers and engineers who built up the product. In some cases, alpha testing is completed by the customer or outsourcing group with the presence of testers or developers.
Beta testing is performed by a set number of end clients before delivery. Normally, it is done in the customer place.
21. What is Risk-Based Testing?
A. To recognize the functionalities or modules which are in all probability to cause failures and to test them.
22.What is Application Programming Interface (API)?
A. A formalized assortment of programming calls and routines that can be mentioned by an application program to access to network systems or supporting system.
Also See Manual Testing Interview Questions and Answers by SendTods
23. What is Agile Testing?
A. Agile testing is a type of software testing practice that takes after the standards of an agile software development. It is an iterative program development procedure where necessities continue changing according to the client needs. Testing is done in parallel with the advancement of an iterative model. Test group gets frequent code changes from the dev group for testing a system.
24. What are the various Methodologies in Agile Development Model?
A. There are at present seven various agile systems that I know about:

  • Scrum
  • Extreme Programming (XP)
  • Feature-Driven Development
  • Lean Software Development
  • Agile Unified Process
  • Dynamic Systems Development Model (DSDM)
  • Crystal

25. Why we utilize the Decision Tables?
A. The methods of boundary value analysis and equivalence partitioning are regularly connected to particular conditions or sources of info.
But if diverse combinations of input end in various steps are made, this can be harder to indicate utilizing equivalence partitioning and limit value examination, which have a tendency to be more centered on the UI.
The other two specification-based methods, state transition testing, and decision tables are more centered around business rules or business logic. A decision table is a decent method to manage combinations of things.
Certain times this technique is additionally known as a cause-effect table. The reason is there’s a related logic graphing procedure known ascause-effect graphing which was at times used to help procure the decision table.
26. What is Load Testing?
A. It is to check that the application/system can deal with the required number of transactions and to confirm the system/application behavior under peak load and normal conditions both.
27. What are the advantages of Test Reports?
A. The advantages of test reports are:

  • Current status of undertaking and nature of software are notified.
  • In case required, partner and the client can make a corrective move.
  • The last report supports to determine whether the software is ready for launch.

28. In incremental testing what are Stubs and Drivers?
The two stubs and drivers are a component of incremental testing. In incremental testing, there are two methodologies to be specifically bottom-up and top-down methods.
Drivers are utilized as a part of bottom-up testing and stub is utilized for the top-down method. With a specific goal to test the principle module, a stub is utilized, which is a dummy program or code.
29. What is Soak Testing?
A. Running an application at high load for a continued timeframe to distinguish the execution issues is termed Soak Testing.
30. What is Performance Testing?
A. This kind of testing decides or approves the speed, versatility, or durability qualities of the application or system under test.
Execution is concerned about accomplishing response times, resource usage levels, and throughput that meet the execution targets for the product or project.
31. What are the standards of Software Testing?
A.

  • Testing indicates the presence of flaws
  • Thorough testing is not possible
  • Early testing
  • Defect clustering
  • Testing is setting depending
  • Pesticide Paradox
  • The absence of error false notion

32. What is a Bug?
A. In the event that software testers discover any contradiction in the application or system in testing stage then they describe it as a bug.
33. What is DFD (Data Flow Diagram)?
A. As a flow of data through a data system is graphically depicted then it is called Data Flow Diagram. It is likewise utilized for the representation of data handling.
34. What is Fuzz testing and when will you use it?
A. Fuzz testing is used to recognize security loopholes and coding mistakes in the product. In this method, random data is added to the application trying to crash the system.
In the event that vulnerability continues, a device called fuzz tester is utilized to decide possible causes. This strategy is more helpful for greater projects yet just recognizes a major mistake.
36. Describe the PDCA cycle.
A. Software testing plays an essential role in the software development method. In a typical software development, there are four vital steps in PDCA: Plan, Do, Check, Act, cycle. The four stages work as
Plan: Describe the objective and the arrangement for fulfilling that objective.
Do: Perform as per those plan methods which is arranged in the planning stage.
Check: Check to ensure that everything is working as per the plan and gets the normal outcomes.
Act: Act as indicated by that issue.
37. What ought to be done after a bug is found?
A. Configuration administration covers the procedures used to control, facilitate, and track: code, prerequisites, documentation, issues, change demands, designs, compilers/tools/libraries/patches, alterations made to them, and who rolls out the improvements.
38. What is SQA testing? Tell us steps of SQA testing.
A. Test Plan has these principal contents:

  • Schedule
  • Resource requirement
  • Due date
  • Financial plan
  • Feature to be examined with reason
  • Feature not to be examined with reason
  • Tools to be utilized
  • Scope of testing
  • Test technique

39. Tell the contrast between a “defect” and a “failure” in software testing?
A. In basic terms when a defect approaches the end client it is known as a failure while the defect is recognized inside and settled then it is called as a defect.
40. Q. Specify what is the reason behind doing end-to-end testing?
A. End-to-end testing is performed after the functional testing. The reason behind performing end-to-end testing is:

  • Testing application in genuine environment situation
  • Testing of association between database and application
  • To approve the product necessities and integration with outside interfaces

41. What is Bug Leakage?
A. A bug which is really missed by the testing group while testing and the build was discharged to the Production. In case that now that bug was found by the end user then we refer to it as Bug Leakage.
42. What is the part of mediator in the review procedure?
A. The mediator or review leader drives the review procedure. The moderator decides, in co-activity with the creator, the sort of review, approach and the creation of the review team.
He or she plays out the entry check and the follow-up on the modified work, keeping in mind the end goal to control the nature of the input and output of the review procedure.
The mediator likewise plans the meeting, scatters reports before the meeting, paces the meeting, mentor’s other colleagues, prompts conceivable discussions and stores the information that is gathered.
43. When should tester perform the Regression Testing?
A. After the product has changed or when an environment has changed Regression testing ought to be performed.
44. What is HotFix?
A. A bug which needs to be managed as a high priority bug and fix it instantly.
45. What is the reason for a test completion criterion?
A. The reason for test completion criterion is to decide when to quit testing.
46. What are the advantages of Independent Testing?
A. Independent testers are unprejudiced and recognize diverse flaws in the meantime.
47. Why are dynamic testing and static testing depicted as complementary?
A. Since they share the purpose of recognizing defects yet vary in the kinds of defect they spot.
48. What is Error seeding?
A. Error seeding is a procedure of intendedly including known errors in software to recognize the rate of error location. It helps during evaluating of the tester aptitudes of discovering bugs and furthermore to know the capacity of the application i.e. how well the application is working when it has errors.
49. What is equivalence class partition?
A. In equivalence class partition, inputs to the system or product are separated into groups that are required to display like behavior, so they are probably going to be proposed similarly. Thus, choosing one input from each group for designing the test case.
50. What is positive and negative testing?
A. A positive testing is a point at which you put in a valid info and anticipate that some activity will be finished as per the specification. While a negative test is a point at which you put in an invalid information and gets errors.
51. Could inspections or reviews be viewed as part of the testing?
A. Yes, indeed, as both assists identify errors and enhance quality.
52. What amount of testing is sufficient?
A. The appropriate response relies upon the contract, risk for your industry, and special needs.
53. Explain Exploratory Testing?
Exploratory testing is based on less planning and more test execution. It refers to performing requirement analysis, test cases designing, test cases execution and understanding the test results simultaneously.
54. Explain verification in software testing?
Verification ensures that the product is being built according to the software requirements, and there are no deviations from it. The verification process involves Inspections, Reviews, and Walk-through.
55. Explain validation in software testing?
Validation ensures that the software product that is built is as per the client’s requirements or not.
56. What is the basic difference between verification and validation in software testing?
Verification detects defects in requirement specifications & validation detects the errors in the implemented Software application.
57. Explain Static Testing?
Static Testing is to review the documents to detect the errors in the initial phases of SDLC.
58. Explain Dynamic Testing?
Dynamic testing is to run the AUT to validate the output from the expected outcome.
59. What are the other names for white box testing?
It is also known as Glass Box, Clear Box, and Structural Testing.
60. What is white box testing?
White box testing refers to the testing of the internal code structure.  white-box testing is done at the unit level and is based on the internal perspective of the code and requires programming skills to design test cases. It tests if the code is written properly and inspects every line of the code for being bug-free.
61. Can you explain about test strategy?
Test strategy is a document that includes test design and defines how testing is to be carried out.
62. Name the components of the test strategy document?
The various components of the test strategy document are

  • Test plan id
  • Features to be tested
  • Test techniques
  • Testing tasks
  • fail criteria/ Features pass
  • Test deliverables
  • Test schedule
  • Test resources and their Responsibilities
  • Testing environment

63. Explain the Test plan?
A test plan defines the goals, resources, and procedures for testing a software product. It includes a thorough understanding of the testing workflow.
64. How will you create a test plan?
Follow the following steps to write a test plan;

  • Analyze the product
  • Design the Test Strategy
  • Clearly defining the Test Objectives
  • Develop the Test Criteria
  • Define how the test environment would be
  • Schedule and Estimation
  • Determine the exact Test Deliverables

65. Explain the term testbed?
The testbed is an amalgamation of hardware and software components that are required to conduct software testing.
It consists of Operating system, specific hardware, and software, the product under test, network configuration, other system software, and application software.
66. Explain the term test environment?
An environment where testers execute test cases is test environment. Software and hardware environment together form a test environment and serves as a podium to conduct testing.
67. Explain the term test Data?
Test data are the inputs given to AUT by the testers to execute test cases and validate the results.
68. Explain test closure?
Test closure document is the final document prepared before testers mark an end to testing. It consists of details like several test cases, test cases executed, defects found, defects fixed, defects not fixed, defects rejected, etc.
69. Explain test coverage?
It the measurement of quantity of testing done by a set of test cases.
70. Explain the term integration testing?
Integration testing is a type of testing where smaller units of code are integrated and tested in a group.
71. What is System Testing?
Known as the end to end testing, system testing validates a completely integrated application to if the system is in accordance with the requirements or not.
72. What is Big Bang testing?
Big bang testing is based on integrating all the modules together and then testing them all at once.
73. What are different strategies of integration testing?
Integration testing can be carried out using two approaches:

  • Big Bang Approach
  • Incremental Approach
  • Top-Down Approach
  • Bottom-Up Approach
  • Sandwich Approach

74. What are the disadvantages of Big Bang Integration?

  • The disadvantages of big bang integration are:
  • Time-consuming
  • Tracing the cause of failures is difficult.
  • Enhanced chanced of critical failures.
  • In case of a bug, finding the root cause of it is difficult.

75. What is functional testing?
Functional testing is a type of black-box testing, which validates that every function of the software as per the requirements.
76. What are the different types of functional testing?
Different types of functional testing are:

  • Smoke testing
  • Sanity testing
  • Regression testing
  • Usability testing

77. Tell the steps to be performed for functional testing?

  • Steps to perform functional testing are:
  • Identify the required functionalities
  • Creation of test data
  • Determine the expected output
  • Execute the test case
  • Compare actual and expected outputs
  • Validate the software works as per required functionalities

78. What is non-functional testing?
It tests the non-functional requirements of the system like the way it operates.
79. What are the different types of non-functional testing?

  • Various types of non-functional testing are
  • Performance Testing
  • Load Testing
  • Failover Testing
  • Security Testing
  • Compatibility Testing
  • Usability Testing
  • Stress Testing
  • Maintainability Testing
  • Scalability Testing
  • Volume Testing
  • Security Testing
  • Disaster Recovery Testing
  • Compliance Testing
  • Portability Testing
  • Efficiency Testing
  • Reliability Testing
  • Baseline Testing
  • Endurance Testing
  • Documentation Testing
  • Recovery Testing
  • Internationalization Testing
  • Localization Testing

80. What are the different types of testing?

  • Different types of testing are:
  • Functional
  • Smoke testing
  • Sanity testing
  • Regression testing
  • Usability testing
  • Non – Functional
  • Performance Testing
  • Load Testing
  • Failover Testing
  • Security Testing
  • Compatibility Testing
  • Usability Testing
  • Stress Testing
  • Maintainability Testing
  • Scalability Testing
  • Maintenance
  • Regression
  • Maintenance

81. Tell the different test levels?

  • The four different test levels are:
  • Unit/component/program/module testing
  • Integration testing
  • System testing
  • Acceptance testing

82. Name the various black box testing techniques?

  • The different black box testing techniques are:
  • Equivalence Partitioning
  • Boundary value analysis
  • Cause-effect graphing

83. What does a test plan consist of?

  • A test plan consists of
  • Test case identifier
  • Scope
  • Features to be tested
  • Features not to be tested
  • Test strategy & Test approach
  • Test deliverables
  • Responsibilities
  • Staffing and training
  • Risk and Contingencies

84. What is retesting?
Retesting is a process of testing the code again to check if the defects detected in the previous round of testing are fixed correctly.
85. What is Data-Driven Testing?
Data-Driven Testing is testing the application with multiple test data. The complete testing is data-driven and the main aim of such type of testing is to verify output for multiple test data.
86. How can you resolve issues during software testing?
We can resolve issues by:

  • Record: the defects are logged and recorded
  • Report: The defects are reported to higher management and the development team
  • Control: issue management process is defined.

87. What is a test scenario?
The test scenario is any functionality of the code that is to be tested.
88. Define test cases?
A test case describes the execution settings, testing method, input data, expected results to attain a testing objective.
89. Define test scripts?
Test scripts are small programs that are run manually to test a specific functionality of the code.
90. Define Latent defect?
Latent defects are the defects that have been present in the code for a long time but have never been detected before in the previous releases.
91. Name two parameters that define the quality of testing?
You can judge the quality of testing by:

  • Defect reject ratio
  • Defect leakage ratio

92. What are the test deliverables?
Test deliverables are the artifacts that are delivered to the stakeholders after every round of testing.

  • Test strategy
  • Test plan
  • Test scenario
  • Test cases
  • Test data
  • RTM
  • Test metrics
  • Test incident report
  • Test status report
  • Test summary report
  • Release note
  • Test closure report

93. What is mutation testing?
It is a technique to identify if test data/test case is useful by knowingly introducing a bug in the code and retesting the bug induced code with the original test data, a test case to check if it detects the bug.
94. What things will you ruminate before choosing automation tools for the AUT?

  • Technical Feasibility
  • Complexity level
  • Application stability
  • Test data
  • Application size
  • Re-usability of automated scripts
  • Execution across environment

95. How to perform Risk Analysis?
For the risk analysis following steps need to be implemented

  • Find risk score
  • Create a risk profile
  • Change the properties of the risk
  • Install test risk resources
  • Create a risk database

96. Can you tell the debugging categories?
The debugging categories are:

  • Brute force debugging
  • Backtracking
  • Cause elimination
  • Program Slicing
  • Fault tree analysis

97. What information should a test plan include?

  • Test Strategy
  • Test Objective
  • Exit/Suspension Criteria
  • Resource Planning
  • Test Deliverables

98. State few risks that can result in project failure?

  • Insufficient resource for the project
  • Improper testing environment
  • Budget constraints
  • Strict timelines

99. How to do project estimation?

  • Break the project into small tasks
  • Assign them to different team members
  • Estimate efforts for each task
  • Confirm the approximation

100. What are the commonly used testing types?

  • Unit Testing
  • API Testing
  • Integration Testing
  • System Testing
  • Install/Uninstall Testing
  • Agile Testing

101. What are the things to consider while monitoring your project?

  • Schedule of your project is going fine?
  • Budget is under the limit?
  • Are resources enough?
  • Are there any warning signs reflecting any future problem
  • Are there any requirement changes?

102. Common mistakes that lead to issues?

  • Improper resource allocation
  • Poor Scheduling
  • Underestimating
  • Ignoring the small problems
  • Not following the process

103. What does a test report consist of?

  • Project Information
  • Test Objective
  • Test Summary
  • Defect

104. What are the benefits of the test report?

  • Gives information on the on-going status of the project
  • Tells about the quality of product
  • Stakeholder can take corrective measures whenever required
  • The final report tells if the product is ready for the release.

105. What are the best practices of software quality assurance?

  • Continuous Improvement
  • Documentation
  • Tool Usage
  • Metrics
  • Responsibility by team members
  • Experienced SQA auditors

106. What steps you should follow after you detect any defect?

  • Recreate the defect
  • Attach the screenshot
  • Log the defect

107. When to Prepare Requirement Traceability Matrix?
RTM is prepared before test case designing.
108. Who prepares the test plan?
Test lead or the test manager prepares the test plan.
109. Give a few examples of the test environment?
Some of the examples of the test environment:

  • Application Type: Web Application
  • OS: Windows
  • Web Server: IIS
  • Web Page Design: Dot Net
  • Client-Side Validation: JavaScript
  • Server Side Scripting: ASP Dot Net
  • Database: MS SQL Server
  • Browser: IE/FireFox/Chrome

110. As a tester what would you do, if you find any defect?
I would

  • Reconstruct the bugs/defect
  • Take and affix a screenshot
  • Record the bugs/defect

111. What is Fuzz Testing?
Fuzz testing is carried out by feeding random inputs to an application under test, to validate if the AUT returns exceptions like failing built-in code assertions, crashes,  or potential memory leaks.
112. Name different test coverage techniques?

  • Various test coverage techniques are:
  • Statement coverage
  • Decision coverage
  • Path coverage

113. Name the important modules of defect report format?
The various components are

  • Module Name
  • Project Name
  • The date defect was detected on
  • Who detected the defect
  • Defect ID
  • Defect Name
  • Screenshot of the defect
  • Priority status
  • Severity status
  • Who resolved the defect
  • When was defect resolved

114. What does COTS stand for?
COTS stands for Commercial Off The Shelf.
115. Why do we use automation testing?

  • Eases the execution of test cases that re repeated
  • Helps in the testing of the large test matrix
  • Supports parallel execution of test cases
  • Is beneficial for long run test cases as they can be left unattended without requiring any human intervention
  • Enhances the accuracy of test cases
  • Saves time and money.

116. Can you tell us the advantages of selenium over other testing tools?

  • Supports various languages including Java, Python, C#, PHP, Ruby, Perl &.Net
  • Supports different OS including Windows, Mac or Linux
  • Supports multiple browsers including Mozilla Firefox, Internet Explorer, Google Chrome, Safari or Opera
  • Easy integration with TestNG & JUnit, Maven, Jenkins & Docker
  • It is an open-source

117. Name the components of Selenium?

  • Selenium Integrated Development Environment (IDE)
  • Selenium Remote Control (RC)
  • Selenium WebDriver
  • Selenium Grid

118. Name the various locators in Selenium?

  • ID
  • ClassName
  • Name
  • TagName
  • link text
  • PartialLinkText
  • Xpath
  • CSS Selector
  • DOM

119. Name various exceptions in Selenium web driver?

  • TimeoutException
  • NoSuchElementException
  • ElementNotVisibleException
  • StaleElementException

120. How will you launch the browser using WebDriver?
We can use the following syntax:
WebDriver driver = new FirefoxDriver();
WebDriver driver = new ChromeDriver();
WebDriver driver = new InternetExplorerDriver();
121. What is Regression Testing?
Regression testing is done to validate that the code changes have not introduced any bugs in the existing code.
122. How does automation testing help in agile methodology?
It helps in maximum test coverage in minimal time.
123. Which all test cases can be automated?

  • Smoke test cases
  • Regression test cases
  • Complex calculation test cases
  • Data-driven test cases
  • Non-functional test cases

124. What is a workbench concept?
It is a way to document how a specific task has to be performed.
125. What are the tasks in workbench?

  • Input
  • Execute
  • Check
  • Production output
  • Rework

126. What strategies you can follow to roll out the product to end-users?
The strategies we can follow are:

  • Pilot
  • Gradual Implementation
  • Phased Implementation
  • Parallel Implementation

127. What does PDCA in software testing stand for?
PDCA in software testing stands for Plan, Do, Check, Act
128. Which all types of testing teams can conduct software testing?

  • Isolated test team
  • Outsource – we can hire external testing resources and do testing for our project.
  • Inside test team
  • Developers as testers
  • QA/QC team

129. What are the shortcomings of monkey testing?

  • They are not realistic
  • Many of the tests are redundant and unrealistic
  • You will spend more time analysing results
  • You cannot recreate the test if you do not record what data was used for testing

130. What does DFD stand for?
DFD stands for Data Flow Diagram. IN DFD the flow of data is represented graphically.
131. What does LCSAJ stand for?
LCSAJ stands for ‘linear code sequence and jump.’
132. Why is test independence done?
Test independence eludes author preference in describing operative tests.
133. When do you define the exit criteria?
Exit criteria are described based on “Test Planning”.
134. What is alpha testing?
Alpha testing is pre-release testing by the end-users at the developer’s end.
135. What is beta testing?
Beta testing is testing done by a selected group of end-users at their location. It is done before the software is out in the market.
136. What are the responsibilities of test management?
The responsibilities of Test management are:

  • To enhance software quality
  • Creating and up keeping the product metrics
  • Ensures that there is less design or coding faults

137. The output of the requirement analysis used as an input for which phase?
User Acceptance Test Cases
138. What are the benefits of Independent testing?
Independent testers are neutral and detect dissimilar bugs at the same time.
139. In reactive testing approach, when does test design work begin?
The test design work in reactive testing approach begins after the software is produced.
140. Name different Agile testing methodologies?
The different Agile methodologies are:

  • Extreme Programming (XP)
  • Lean Software Development
  • Unified Process
  • Scrum
  • Feature-Driven Development
  • AgileCrystal
  • Dynamic Systems Development Model (DSDM)

141. Which process involves the estimation of the testability of the requirements and system?
‘Test Analysis’ and ‘Design’
142. Name a few dynamic testing techniques?
Equivalence Partitioning, Use Case Testing, Exploratory Testing, and Decision Testing are dynamic testing techniques
143. Name a few static testing techniques?
Data Flow Analysis and Inspections are static testing techniques.
144. Which testing technique detects threats such as virus from malicious outsiders?
Security Testing detects threats such as virus from malicious outsiders
145. When to implement configuration management procedures?
During test planning.
146. What is an equivalence partition?
Equivalence partition is dividing input and output values in a range such that only one value becomes a test case.
147. What is load testing?
Load testing tests the system performance under real-life load conditions.
148. What is stress testing?
Stress testing tests system performance under unfavourable conditions/loads.
149. When can you take a conclusion to end software testing?
Some of the basic criteria to stop testing are:

  • Deadlines are finished
  • Test budget is over
  • Bug rate is less than a certain level
  • Passed Test cases percentage is above a pre-decided level
  • Testing period for Alpha or beta testing is over
  • Code Coverage, requirements are met to a required level.

150. What’s the difference between a SDET and Tester?
software testing interview questions
151. What’s interrupt testing?
Interruptions happen on our phone frequently. These sudden interruptions can have adverse effect on regular functioning of any app that’s being used.
Interruption testing will reveal how the app behaves to interruption and will it get back to the stopping point without any error?
All the best!!!
 

How To Write an Impressive Software Tester Resume

Posted on by tbsupadminnxtbackendacc

Your resume have to create an impression for them to consider you, hence, a killer software tester resume is important. Listed here are the major factors that you have to consider while writing a software tester resume.

Put an impression

The resume is similar to an advertisement if it is attractive enough to pursue an audience than it is worth making a sale.

This will demonstrate the skills and education scenario of an individual in a proper manner.

If the resume is worth working for then they might give you a call for work.

However, you only have 5 seconds to a minute to attract an HR in this competitive world.

It is important to get the resume made with accuracy and precision to get the most awaited call from your HR.

In order to achieve it, one must have a unique resume that makes HR call for them immediately.

It is your opportunity to get the most done within a limited time frame. With so much of task in hand, the recruiters don’t usually check out every single detail in a resume.

They will just have a brief scan of the whole resume and will decide your future with them.

In order to get this done with results, one must have an organized, appealing and error-free resume.

Make a Good Impression

With a limited time frame, one must have the ability to capture their essence in a single or maximum two sheet.

This will allow one to easily process with the whole professional qualification with a tint of personal life.

In order to give this snapshot, one must take the helpof pointers that allows an easy explanation in one work without description.

Especially, if the soft tester is a fresher then it becomes more important to make the resume attractive with no prior experience with work.

Start with the Basic

Instead of simply writing the resume, one can start with basics or consider is pre-activities.

  • Make a proper list that must contain all the information about work experience, education, skills, projects, technologies, a platform to work on, certifications, diplomas, etc.
  • You don’t have to work on the format in the template and initial stage. Simply use a notepad or sticky notes to get every single detail together. It will compile all the details about you on a single page.
  • Make a list as the Technical skills containing –JIRA, Manual Testing concepts, BN Scripting beginners, etc. Then move towards education point that will contain 10th, 12th, graduation, post-graduation, etc. details. Similarly, add on the company experience (if any) in one part from the starting of the career till now. It must contain year, company name, designations, key responsibilities, project details, etc.
  • Then, pick a list one by one, say technical skill then sort them up as per the proficiency in that skill. You can say that the rating of every single skill will be done out of 5, the thing you are best at will have 5 marks whereas the familiarity prospect only has 1.
  • Go through the whole list once you are done, every single part and make sure that you have not missed out some important part. If yes, then add them or make a new column as certifications that can add your certificates details.
  • Then try to see your weakness, just because you are trying for the tester’s job doesn’t mean that you will have it with the blink of an eye. It is essential to know where you are lacking and the area that you need to work on.

Once, the details are compiled together then comes the template part to give it the proper flow.

Fresher or Experienced Resume Format

Now, you have all the details that are required to set in the resume. You need to move towards the setting up the point that will require proper formatting.

Also Read: Salary Of Software Tester 2019 (USA,Canada,UK,India)

You need to highlight the important point and cover up the weakness in such a way that makes it more attractive. The format that is usually followed by the IT professionals are:

  • Header – Start with the Name at the top with the e-mail address, address and phone number right below it. These are the main attributions and means of communication for the testers and hence must be visible easily. You can also add a link to some certification or professional network that you are connected with such as LinkedIn profile.
  • Objective or Career Snapshot – It is a single line that explains everything about you. What you want, where you want to reach and what are your career scope. In order to get into the Software testing jobs, you have to focus on the transition that can be elaborated in this field.
  • Summary – This part will contain all the details in brief format that can be tabular or bullet point’s form. It will have the certifications, awards, achievements, technologies, etc.
  • Educational Background – This part will contain the education prospect of an individual. This must have the post-graduation and then graduation details. Move to the 12th and 10th background details. You don’t have to move further, just mention the school name, year and percentage that one achieved in the higher to lower education form.
  • Professional Background – If you are an experienced individual then it is essential to fill out spacewith the main career and professional background. It must contain the company’s name, role, strength, project, etc. Also, start with a significantpoint or your present working details then move towards your first job. Everything must be in the backward direction.
  • Project – This is an essential part since it will contain everything that you might have done in your professional life. However, you need to start with the recent project and then move towards the other one as the professional background.
  • Certifications – It must contain all the certification that you are involved in. However, you don’t have to fake anything since companies can ask for the proof. Hence, it is better,to be honest with the section.
  • Technical Skills –This section must contain the information about the technical skills that are acquired by the employee. It can while doing the job or some other skill that one might have.
Writing the Project Format

Yes, while you are mentioning the project that you might have done in the professional end, you need to follow a certain pattern to it as well. In the whole details format, there are major headers that you can’t missout.

  • Project Name
  • Name of the client or company (optional)
  • Description of the project in 2-3 sentences that can give us an overview of the whole project.
  • The environment in which the project was completed that is codinglanguage, tools, etc.
  • Size of the key
  • The key responsibilities that are handled by you personally.
Year Gap

Year gap is no longer a frustrating thing in the market. Even the employers understand the reason to have a gap in any profession.

Also Read: Software Testing Companies are Plenty. Know Why Testbytes is the Best Choice For You!

All you need to do is mention why you have a year gap. In the place of the gap, one can mention the freelancing work or certification work that they might have done.

This will only add value to the resume since they will not your hard-working nature. Also, you can try to convince the interviewer later on that it was a valid reason to have a gap such as relocation, maternity, business, holiday, etc.

Accomplishment

You must try to cover up everything in a single sheet of paper but if it is not possible then one must put in some of the major snapshots of their career in the first sheet.

Employers don’t actually reach out to the next sheet if there is nothing to hold their attention on the first page.

Hence, make sure to mention all the accomplishment in the single sheet to grab their attention.

It can be in terms of education or certification or maybe the professional background. You can mention the extra details in the second sheet.

Things to keep in Mind

While writing an attractive resume, you need to know that:

  • Brief and simple resume has more value thanstack up and colourfulresume.
  • The objective must be clear and not confusing since it will be the first thing an employer notice.
  • Relevant skills must be highlighted or you can bold them to make sure that employers have a look at them.
  • No need to add unnecessary information such as Father’s detail, age, weight, etc.
  • Resume and Curriculum Vitae at the top of the resume are long gone trend.

What is Soak Testing? Definition and Examples

Posted on by tbsupadminnxtbackendacc

Software systems are subjected to heavy loads continuously. Google Search is an apt example of such scenarios. But what if such software breaks after a certain time of bearing heavy loads? It can affect large masses of people and can even break their trust in the software. Hence it is very important to ensure that such heavy load software are aggressively tested. To test software for heavy load for over a continuous time, we require soak testing.

What is Soak Testing?

Soak Testing is a type of performance testing where the software under load is tested to validate that it can endure heavy loads for the extended period.
Why Should You Perform a Soak Test?
Soak testing is very important and is conducted to recognize and augment possible issues like memory leaks, resource leaks, or deprivation that can happen over time due to constant heavy load over the system.
Prevention Is Better Than Cure
It is very essential to reduce performance errors and system errors from the system. Soak testing loads the system with a heavy load for a continuous period, hence determining its ability to sustain heavy loads for a long period. This type of testing is important for a website that bears a heavy load for a continuous time frame. Some of such websites are search engines, social media sites, etc.
The main Objectives of Soak Testing are: 

  • One of the main objectives of soak testing is to validate software behavior when subjected to heavy loads for a continuous long time.
  • Another main objective is to predict system failure during heavy load conditions.
  • Soak testing also validates the performance of the system.
  • It also validates the system is dependable and steady.

When is Soak Testing done?
Soak testing is a complicated job and is very time-consuming. Hence it should be carried out in a particular time so that no other testing activities are disturbed and the complete software testing process goes on smoothly.

  1. Soak testing is better to be conducted after load testing. Before the build is installed, and it is gone through a series of load tests at high traffic levels. After the accomplishment of load testing, a round of soak testing is done.
  2. Soak testing requires a lot of time to be executed, sometimes the soak tests last for full day and night. Hence soak testing should be performed at a time, when it does not hinder any other testing activity. The weekends are the best times for conducting soak testing, as the testers can execute the soak testing test cases and can let it execute over the weekend.

Concerns in Soak Testing
Soak testing is a time-consuming process; hence keeping in mind the duration of executing its test cases and amount of test data, few considerations has to be taken before executing soak testing. Here are a few considerations for executing soak testing:

  • How long do you have to execute soak testing, is one major question when considering soak testing. It is very important to decide what time frame you will consider for soak testing. The execution time of soak testing is generally decided by the availability of the system for conducting soak testing and delivery deadlines.
  • It should be very well considered that each application can execute without any interruptions during the execution of soak testing.
  • It should include all the scenarios decided during the requirement phase based on customer’s requirements.
  • The maintenance window time is a major aspect in determining the scope of soak testing.

Read also : What is Waterfall Model? Pros and Cons

What are the failures that are detected by Soak Testing?
The soak testing is very important, it helps in validating software for bearing heavy load for continuously long periods. The soak testing helps in the detection of issues like:
Memory Leaks:
Soak testing helps in the detection of some of the major issues which can even lead to the system crash. It helps in the detection of serious memory leaks which can not only crash the application or the software but can also crash the complete operating system in which the application runs.
Layer Connections Failure:
There is a very close connection between the layers of the software or the system, and defect or failure in these connections can lead to an interruption in the complete module. Soak testing helps us detects any such failures of connections between the layers of the system.
Database Connections Failure:
Under some situations, soak testing can also detect database connection failures. These failures can result in crashing of the complete system, and hence detection of such failures is very important, soak testing assists us in the detection of such Database Connections Failure
Response Time Degradation:
One of the major issues that heavy loads can lead to is losing the efficiency of the system by increasing the response time. Soak testing helps in the detection of such response time degradations, hence giving the developers a chance to fix this issue to make the system free from any Response Time Degradation issues.
Soak Testing Strategy
Strategy plays a very important in software testing. it is equally important in soak testing as well. It is very important to strategize your soak testing efforts before actually executing the soak testing:

  • Testing Environment:

Setting up of testing environment is one major phase of software testing. It helps analyse the software, hardware, operating system, and database on which the tests have to be performed. In soak testing also creating up of test environment is very important and plays a major role.

  • Test Scenarios:

Soak testing is a very wide process. It is also very time consuming, hence it becomes very important to plan, analyse, and conclude the test scenarios before executing soak testing test cases. The development team also play a major role in determining test scenarios by letting the testing team know the amount of load that can be adhered on the system.

  • Test Estimation:

Soak testing as discussed earlier is extensive testing. It requires long hours to execute soak testing test cases. Though, this duration of execution may vary according to the scope of the system and participation of the development team, clients, and more.

  • Risk Analysis:

The probable risks and issues are analysed to conduct soak testing.
Soak testing tools
The list of tools that can execute is pretty long. Mainly the tools used for load testing are also used for soak testing by setting up the load and durations field in the test tools.

Read also : What is Data Breach? How to Prevent Data Breach

Some of the automated testing tools that can assist in soak testing are LoadUI, Apache JMeter, Appvance IQ, WebLOAD, and various plugins on Jenkins and GitHub.
Advantages of Soak Testing
Soak testing is very important and has many added advantage in delivering a defect-free system:

  • It ensures that capabilities of the software system.
  • Soak testing helps in finding defects that cannot be detected by the performance testing
  • It helps in making the software system more robust by detecting the defects that can be induced in the software due to continuous heavy load conditions.
  • It validates the sustainability of software system over a time period.
  • The soak testing results are used to improve the client-side infrastructure and hardware.

Disadvantages of Soak Testing
Soak testing has many advantages, but as every coin has two sides, soak testing tools has many advantages and few disadvantages. Though these disadvantages do not affect the soak testing test results but are essential to be considered before executing soak testing.

  • Soak testing is a very time-consuming process and can even take a couple of days and nights to execute it. Such a long process can result in delayed product delivery and hence executing soak testing or not has to be decided based on the time limitations of the project.
  • Running soak testing manually is a very bad idea as soak testing is a time-consuming task and also requires a large amount of data. Doing it manually can result in wrong test results and hence it is must to execute soak testing using the automated tools.
  • It is very important to detach live environment from the test environment while executing the soak testing, as any anomaly in executing the soak testing can corrupt the complete live environment resulting in data loss or data corruption permanently.
  • Determining the extent of soak testing to be performed is very difficult. You can hardly get an idea of how much soak testing has to be performed to give the best results.

Examples of Soak Testing
Search engines are an apt example for soak testing. Search engines are continuously used by millions of people around the world. Search bars keep lying idle for few on their mobile handsets, for few they have some search typed over but are left unattended and few are rigorously searching for information over search engines. These search engines are a must to be tested for soak testing.

The Banking software is continuously tested for load for around 70 hrs to 150 hrs. They are induced with large data and are uninterruptedly tested for long hours.
Similarly, there are many other applications and software that experience heavy loads for long hours. Executing soak testing for them is very important to ensure the utmost safety of the system. Some of this software are social media sites, gaming sites, etc.
Conclusion
Soak testing is a type of performance testing that validate that software can tolerate heavy loads continuously for long durations. Although it is very time consuming and requires a large amount of data, it is very important to execute soak testing to ensure the high-end performance of the software system.
soak testing pdf

My Journey as a Video Game Tester

Posted on by tbsupadminnxtbackendacc

Hi, my name is Hari Panicker. A passionate video game tester, Also, I am a die-hard fan of playing (Role-Playing, Adventure, MMORPG & arcade games.  My unmeasurable love towards game is the main reason why my career as a video game tester flourished.
It all started with the game called Contra and Dangerous Dev in my 4th standard.
The game was so interesting that after school I used to dash towards home to complete my homework then sit and play till bedtime without even flinching. Ah! How can I forget?
As I grew up I discovered more and more intense games like CS, Dota I, Red Alert, AOE (Age of Empires), GunZ the Reloaded Duel and many more. Among the huge list, hands down my favorite, the one, and only Ragnarok Online.
About the game, Ragnarok is an MMORPG created by Gravity. I was so into this game that I used to sometimes skip my study hours for playing the game with my friends (lol..).  I and my friends used to party up and level up our characters, hunt equips /attribute card from morning till noon.
Then in the evening, we party up again for some PVP (Player vs. Player) and GVG (Guild vs. Guild) fights. It was not just playing the game for me and my friends we started to make money by selling some rare items in-game which was very hard to obtain.
After a few years, the game server closed so I had to move to another Ragnarok server. This was a Malaysian Server called Happy Ragnarok Online. I was the No.1 Player of the server which gave me the opportunity to work as a Game Master for this game.
From there my Game Testing life started I had to report Bugs, find out who is using Cheat (Botting) result to permanent BAN and Ragnarok Support (Help players if they have any questions regarding the game).
Moving on I realized that my career is into Game Testing and further started to work in a game testing company where I got to learn many new things about games and how it works (many new terms used in-game, writing bugs, uploading them on Jira, Mantis, etc.) in testing.
Within 6 to 7 months I got promoted to a Senior Test Engineer where I had to handle a team of 8 to 15 people, explains them the task to do, solve their queries about the game, review the bugs properly and send daily status reports.
Games I have tested:

My team had good times and bad times in projects we tested. we were gifted with immense pleasure when the tested game gets positive feedback from the clients with some Goodies (Gifts) 😊, and of course, there is a lot of pressure when the delivery date approaches. But yes, after all, its fun testing more and more games 😊

My craving for games and testing them will never end. It’s like my hobby turned in to my career.

How to Get a Job In QA Testing Company? Essential Traits and Techniques

Posted on by tbsupadminnxtbackendacc

Why QA testing job can be a good career choice
If you are in a confusion in deciding after your graduation whether to choose Software Testing as a career, then the below points can strengthen your judgment to choose software testing as a career.
In case you are already employed in a Company as a Software Tester and worried about your career growth then these points confirm that you have chosen a right career path.

  • High demand for testing

Testing has become an essential process when it comes to validation of any software. Since software always have a market, testing will also do. So does testers

  • Designing experiments

A QA tester is that mad scientist who designs and performs elaborate experiments to bring out the real quality and real capabilities of the software.

  • Remuneration

Remuneration is one of the biggest highlights of this profession. Even though freshers have less, as experience increases payscale also increases.
Read this blog to know more about software tester remuneration of 2019

  • Code Writer

It is an old myth in an industry that anyone who cannot code can be a Software Tester. But this being an automation age, a QA tester adopts writing code to automate the scripts.

  • Growth and multiple routes towards progression

Speaking about career growth, a Tester will eventually become Test Lead, and then  Project Lead,  and then Automation Architect,  and then Test Manager etc., Ultimately everyone in this path reaches to the manager level.

  • The scope of Exploring the Latest Technologies

Being a tester and as the process entails, you will be required to work with all the latest techniques and technologies. So you get well versed with the popular and prevalent testing tools.

  • Creativity and Innovation

Since testing work is not explained to you, you will need to analyze the clues and think of places where the application is inconsistent with the end-user. So that generates creativity and innovation in you.

Summarily, if you like solving logical puzzles, if you love helping others in releasing a quality product in the market or if you love to take challenges in exploring and struggling to understand and find bugs and reporting to fix them, QA testing job is the right choice for you.
Skill sets required for a QA testing job
Certification
You need to pass the foundation course in QA testing. You should be well accustomed with the QA Testing methodologies, terminologies,  and various testing techniques so that you will be familiar with the different development models (or methodologies) such as waterfall, the V model, incremental, spiral and more frequently these days, the Agile processes.
Test Techniques
You need to have full knowledge of all the testing techniques.
Documentation and Testing process
You need to know how to obtain conditions from the required document, ways to devise test-cases from the test conditions and ways of writing test procedures.
Testing Tools
You need to have knowledge and experience on Automation Testing Tools, Performance Testing Tools, Test Management Tools, and Bug Tracking Tools.
Personality and Attitude towards testing
As a QA tester, your job is to check to see that the project is running according to the design and specification and you should report any variation from the documented scripts. Hence, a great deal of concentration, comprehensive investigation and proper recording of results are very important. A good tester must possess the ability to take advantage of any security risks and exhibit that the output is fit for release.
Other attributes required are:

  • A good memory to reproduce the unscripted steps
  • You need to be a good communicator and team player to discuss any defects found to other members of the team
  • You need to be Ethical


Tips on getting a QA testing job easily

  • Update your resume

Make sure you take the time to think back about all your relevant past year work experiences. Do not try to show off. Organize your resume accordingly.

  • Get feedback on your resume before submitting

Ask others to review your resume because often a second eye may notice formatting or grammatical error.

  • Develop your Minimum Viable Job

When trying to decide between two competing offers, look out for aspects like geographical location or industry.

  • Create a list of potential employers and companies

Make a list of all the companies you would like to work for and then decide whether you want to move on to a smaller company or join an organization that has an established QA and testing practices.

  • Grow your network, tap coworkers, QA groups and LinkedIn

Confirm with other QA professionals from their LinkedIn profiles to get an idea of how to present your skills and experience and be sure to have your LinkedIn profile at par with your updated resume.

  • Benchmark the company’s QA and testing practices

Identify the best employer by finding out the future goals and current QA practices and methodologies.

  • Do not be too quick to say “yes” to the hiring manager

Get a thorough understanding by paying attention to every step of the job search process prior to confirming your acceptance of the role to the hiring manager.