Software Training Institute - Testing Tools, Selenium, Full Stack Training in Hyderabad

1. Top 20 Interview Questions and Answers in Manual Testing www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

2. 1.What are Software Development Life Cycle Phases? SDLC is a framework that describes the activities performed at each step of a software development project. Planning Analyses Design Coding and Implementation Testing and Integration Maintenance www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

3. 2.Explain Spiral Model? The software engineering team adds functionality for the additional requirement in every-increasing spirals until the application is Ready.When client requirements are enhancing regularly organization can follow spiral model: Planning Risk analysis. Engineering. Evaluation. www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

4. 3.What are difference between bug, error, defect & failure? Bug: A defect reported by tester is accepted by developer, called as bug. Error: A mistake in code, found by developer is called as error/flow. Defect: A mistake in sprint/software found by tester during testing, called as defect/ issue/ ticket. Failure: An issue raised in sprint/software in client site/production, called as failure or latent bug . www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

5. 4.Functional Vs. Non-Functional Testing? Functional testing: In general scrum team testers can start testing (test execution) from functional testing. Here, scrum team testers can validate sprint build with respect to requirements of client. So, this stage of testing called as requirements testing. Non-Functional Testing: This stage of testing also called as System Testing because functional tests are applicable on partial/complete sprint. These tests can validate sprint according to client expectations like usability, compatibility, security, performance & multiple testing. www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

6. 5.Explain for Incremental model? During the first one-month phase, the development team worked from static visual designs to code a prototype. In focus group meetings, the team discussed users’ needs and the potential features . Implementation consisted of four-to-six-week cycles. Software delivered for beta use at the end of each cycle. The entire release took 10 months from definition to manufacturing release. www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

7. 6.What is regression testing? A regression test is a system-wide test whose main purpose is to ensure that a small change in one part of the system does not break existing functionality elsewhere in the system. It is recommended to perform regression testing on the occurrence of the following events: When new functionalities are added In case of change requirements When there is a defect fix When there are performance issues In case of environment changes When there is a patch fix www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

8. 7.What is Fish Model? Fish model is time-taking and costly but quality guaranteed. Due to this reason organizations are using this model to develop software related to Robotics, Satellites,Medical equipment Verification: Review of documents like BRS,SRS,HLD/LLD’s. Validation: Test programs, interconnections and software. BRS: Business Regiments Specification SRS: Software Requirements Specifications Unit Testing: Testing a program www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

9. 8.What is Smoke Testing? Select few positive functional test cases related to main functionality of sprint. Consider those selected test cases as a fixed set for further test cycles in current sprint for smoke test. Run on every sprint build after receiving from developers to ensure that sprint build is working or not. If smoke test failed, reject that sprint build and wait for stable sprint build. If smoke test passed, go to real testing in cycle#1 and go to retesting in further cycles. www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

10. 9.What is Recovery Testing? This testing is also called as reliability testing. During this test scrum team can create wrong environment to run sprint build and then testers can observe that sprint recover from abnormal state to normal state Ex:- a. Decrease network board width. b. Remove network connection. During operating sprint build. c. Sudden shutdown the system. www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

11. 10. Unit Testing/Component Testing? When documents are baseline (finalized/reviewed), scrum team developers can start coding/ implementation. In this stage Scrum team developers can develop programs & test each program like shown below Basic paths coverage. Control structure coverage/debugging. Program techniques coverage. White box/Glass box/Clear box techniques. Mutation coverage/debugging   www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

12. 11.Explain to the Integrating Testing? When related programs are base lined the corresponding scrum team developer can interconnect these programs to build a software (sprint build). Here scrum team developers can test interconnections of programs & integration testing scrum team developers can follow below approaches: Top down approach. Bottom up approach. Hybrid approaches. System approach/Big bang approach. www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

13. 12. Types of testing, stages, phases? Documents Testing (Static Testing/Verification). Unit Testing/Component Testing. Integration Testing. Sprint/Software Testing. User Acceptance Testing. Release Testing. For Testing Maintenance. (Support Team/Services) www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

14. 13. What is Performance Testing? Performance means speed in process of sprint/software. When multiple users are accessing sprint/software at a time (currently/parallelly). During performance testing scrum team testers can use cloud for load runner or Jmeter user using some tools. The execution of sprint/software client expected configuration environment by applying client load to estimate “speed in process” is called as load testing. The execution of sprint/software client expected configuration environment by applying client load for long time to identify “memory leakages” is called endurances testing/durability testing. www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

15. 14. Software Testing/Testing topics? When sprint build is ready, scrum team testers can take that sprint build and conduct testing in two stages. Sprint/Software Testing/QA www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

16. 15.What is white box testing, and what are the various techniques? In white-box testing, tester knows about the code and structure of the application. Hence this type of testing is often known as glass box testing. Mostly, this type of testing is used by developers to perform unit testing. There are various white-box techniques that can be used by the tester to find bugs and defects. Decision Coverage Statement Coverage Condition Coverage Multiple Condition Coverage www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

17. 16.What is black box testing, and what are the various techniques? Black-Box Testing, also known as specification-based testing, analyses the functionality of a software/application without knowing much about the internal structure/design of the item. The purpose of this testing is to check the functionality of the system as a whole to make sure that it works correctly and meets user demands. Various black-box testing techniques are: Equivalence Partitioning Boundary Value Analysis Decision Table Based Technique Cause-effect Graphing Use Case Testing www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

18. 17.Responsibility of Product Owner? Select by higher management of IT Company & approach by client and stack holders. Gathering all requirements as detailed user stories. Sit with SHS, SM, ST, and Select some user stories from all user stories. Participate in daily SCRUM meet in sprint review meeting to collect feed back from client on every sprint Participate in Product backlog refinement meeting to take changes for upcoming sprint. Adjustment of user stories with respect to importance (priority), size (T-short) & complexity in these user stories for sprint to sprint. www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

19. 18.Explain to the V-Model? www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

20. 19.Prototype Model? When requirements are not clear organization can use prototype model from this model, us can develop sample software with screens and with out functionality called if as prototype. After getting full clarity on requirements organization can start real software development. www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

21. 20.Agile Scrum Process? www.magnitia.com | info@magnitia.com |+91 6309 16 16 16

22. Thank you MAGNITIA IT 304 & 305, Paradigm SSS Square, Kothaguda X Roads, Opp to AMB Cinemas, Hyderabad - 500 081. +91 6309 16 16 16 www.magnitia.com FOLLOW US /magnitiaonline /magnitiaonline /magnitia /magnitia /magnitia www.magnitia.com | info@magnitia.com |+91 6309 16 16 16