Course Software engineer Fresher and experienced candidat

Interview questions for manual and automation testing 1) What is a software? Different types of software? • In short computer software is a set of programs, procedures, functions, associated data and/or its available documentation. i) System Software ii) Application Software iii) Client server Application iv) Web based application v) Mobile application 2) Describe the differences between client server and web-based application? • For client server application the software must be installed in the client’s machine. Client server application built on two tier architecture. • Web based application can be accessed through a browser. Web-based application is usually built on multi-tier architecture 3) What is Software Quality Assurance (SQA)? • SQA involves the entire software development process. • Monitor and improve the development process. • Making sure that the requirement matched with the expectation. • Ensure if there is any bug, we fix it. • It is oriented PREVENTATION. 4) What is Software Testing? • Software testing is a process to evaluate the actual software product matches expected requirement to makesure the software product is bug free. • I intentionally do negative and positive testing if there are any fixes required. • It is mostly focused on DETECTION. • Example: I can give you an example of negative testing and positive testing. Let’s say I want to log in to the Facebook account and I put the wrong username and password and my expectation was to get the failed result and it meets my expectation which is called negative testing. And positive testing is exactly the opposite where I put the valid username and password to get successful result and met my expectation which is called positive testing. 5) What is main goal of software testing? • The goal of Software Testing is to ensure the quality of the software that meets the expectation of production needs which compare the User Requirements to developed product. 6) What is SDLC? • SDLC referred to as the Software Development Life Cycle. • It is the process of developing software through business needs/requirements. 7) What is SDLC used for? • SDLC useful in developing the products or customer which ensures the high quality and efficient. 8) Describe the phases of Software Development Life Cycle? • Phases of SDLC: The entire SDLC process divided into the following stages: i) Phase 1: Planning and Requirement Analysis ii) Phase 2: Defining Requirements and designing architecture iii) Phase 3: Building or Developing the Product iv) Phase 4: Testing the Product v) Phase 5: Deployment and Maintenance 9) What are the different types of SDLC methodologies? • Waterfall methodology. • Agile methodology. • Incremental Model. • V-shaped model. • Kanban. 10) Describe the differences between Waterfall and Agile Methodology. • Waterfall: i) Waterfall is sequential methodology where each phase of the SDLC is completed chronologically. ii) In waterfall the development cycle is longer. iii) In Waterfall detailed documentation plays an important role. iv) It’s hard changing the requirements once the project development starts. • Agile: i) In Agile is an incremental methodology where all the phases of SDLC occurs at the same time. ii) In agile the cycle is broken down into smaller sprints each lasting 2 to 3 weeks. iii) In agile preferred discussion and continuous improvement. iv) Agile allows changes in project development requirement. 11) How would you strategize a release in Agile? • I will have the daily scrum meeting to discuss on what each team member is working with. • A sprint planning meeting to discuss the backlog and decide which user story will be developed in this sprint and tested. • Sprint review or demo meeting where QA team show to the product owner stories that were developed, tested and ready for release. • We also have a retrospective meeting to discuss how to improve our agile development this is the way to have a release in an agile project. 12) What is Scrum? • Scrum is a software development process framework for project management based on Agile Methodology. • Scrum uses self-organizing cross-functional teams to incrementally develop products in short cycles. 13) What are the roles in Scrum? • The roles in Scrum: i) Product Owner ii) Development Team iii) Scrum Master iv) End Users 14) What is a Sprint? • Sprints are core components of the agile methodology. • Sprint is the basic unit of development in Scrum which progress via iterations called Sprint. • It lasts from two to three weeks. 15) Describe Scrum Development Process? Or What are the meetings you attend in your Agile methodology? • Backlog grooming: As an on-going activity, the product owner and the scrum team should be actively reviewing their backlog and ensuring the work is appropriately prioritized and contains clear information. This allows each piece of work to be more easily planned into a sprint as it can be more accurately estimated. As a tester I actively try to be involved in this process as it is my first opportunity to assess the requirements and the information provided. It also allows me a chance to gather information required for testing, which allows me to provide more reliable estimates. • The objective is to be in a position where for any piece of work presented in planning you know exactly what the work requires. You should then have a good idea of what you will test and therefore provide reliable estimates. If this is not the case, then the work cannot be effectively planned into the sprint. • Sprint Planning meeting, Daily Scrum Meeting, Review Meeting, Sprint Retrospective. • A SPRINT PLANNING MEETING is the starting point of Sprint. It is the meeting where the entire scrum team gathers, the SCRUM Master selects a user story based on the priority from the product backlog and the team brainstorms on it. Based on the discussion, the scrum team decides the complexity of the story and sizes it as per the Fibonacci series. The team identifies the tasks along with the efforts (in hours) which would be done to complete the implementation of the user story. • On each day of the sprint, all team members attend a DAILY SCRUM MEETING for 15 to 20 minutes to provide updates on the workday before, the task they will perform today and highlight any obstacles. • At the end of every sprint cycle, the SCRUM team meets again and demonstrates the implemented user stories to the product owner. The product owner may cross verify the stories as per its acceptance criteria. It’s again the responsibility of the Scrum master to preside over this REVIEW MEETING. • SPRINT RETROSPECTIVE is conducted at the end of each sprint with the entire team including Scrum Master and to discuss what went well, what did not go well and what steps should be taken to improve the process. 16) What is Defect/Bug? • Defect is the unusual behavior or problem in the software program. • It’s a condition when a product does not meet the requirement or end-user expectation. 17) What are the few types of defect? • Arithmetic, • Logical, • Interface, • Syntax, • Multithreading. 18) List the most popular bug tracking tools available in the market? • Most of the organization uses a defect tracking tool like Quality Center, Jira, Bugzilla, Team Foundation Server, and Clear Quest to report the software problem. 19) What should you do after finding a defect? • RECREATE THE DEFECT: Once you find a defect, we must try to recreate (meaning that we should be able to reproduce it) at least 3 times so that we are sure that it is a defect. • ATTACH THE SCREEN SHOT (SUPPORTING DOCUMENT): Once we confirm that it is a defect, and then it is a good idea to attach supporting documents when we log (write) a defect. For example, screen shot, requirement document etc. • LOG THE DEFECT: Now, the next step is, we need to log it. Depending on the company what kind of tools they are using. In some cases, Excel sheet is used log defects. 20) Explain Bug Life Cycle? • When the bug is logged it gets NEW status • When the bug is accepted it gets OPEN status • When the bug is assigned to developer it gets ASSIGNED status • When the bug is being fixed it gets “In Progress Status” • When the bug is fixed it gets “DEV COMPLETE” or “FIXED” status • When the bug is tested and passed it gets “VERIFIED” status • If a decision is made to fix the bug in later release it gets “DEFFERED” status 21) What is the biggest bug you find out in your last projects/framework? • I cannot go details about the project based on the confidentiality of the company. • But I can tell you when I was logging in to recently, I saw a null error and assign to developer. 22) What is STLC? • STLC stands for Software Testing Life Cycle which performed by the testing team to ensure the quality of the software. 23) Different stages of STLC? • Requirement Analysis – it should be clear, consistent, and testable. • Test Planning – developing the test cases and manage them using tools. • Designing/Development – developing the test cases based on the requirement. • Environment Setup – when integrated environment is ready to validate the product/test case. • Execution – we execute the case in real time and try finding bugs. • Closure – once testing is completed. Matrix, reports are ready to publish/share with the team. 24) Difference between SDLC vs STLC? • SDLC i) Concept – Business Analyst gathers requirements. Development team analyzes the requirements. ii) Requirement – the development team starts analyzing from the architecture and the design perspective. iii) Design Stage – The architecture of SDLC helps you develop a high-level and low-level design of the software based on the requirements. iv) Development Stage – Development team starts developing the software. Integrate with different systems. Once all integration is done, a ready to test software or product is provided. v) Testing Stage – The actual testing is carried out in this phase. It includes unit testing, integration testing, system testing, defect retesting, regression testing, etc. vi) Implementation & Maintenance - Once sign-off is received from various testing team, application is deployed in prod environment for real end users. • STLC i) Concept – no active involvement but can participate on meetings. ii) Requirement – read requirement document try to understand as requirement: clear, consistence and testable. iii) Design Stage – read design document, writing test cases based on design prototype of application. iv) Development Stage – black box tester not active but white box tester do unit testing. v) Testing Stage – all testing needs to do in this stage with manage Defect Life Cycle. vi) Implementation & Maintenance – do regression test if any update version or defect fix. 25) During SDLC, what is your role? i) Discuss with the BS and requirement are clear, consistent, and testable and have the required acceptance criteria. ii) Design phase – write the test cases. iii) Develop – help the developer with unit testing if you are a white box tester. iv) Testing – executing the test case v) Deployment – Regression Risk and fix 26) Difference between Use case and user stories? i) Use Case: (1) Used in Waterfall Methodology (2) Very detailed (3) It is documented in the FRD (4) Time consuming to create (5) Format: (a) Use case name (b) Description (c) Pre-condition (d) Post-condition (e) Basic path (f) Alternative paths (g) Exception path ii) User stories: (1) Used in Agile Methodology (2) Less detailed (3) It is logged onto the JIRA tool (4) Relatively faster (5) Format: (a) As a WHO I want WHAT So that WHY (b) Acceptance Criteria (i) Given (a context) (ii) When (an event) (iii) Then (an outcome) (c) Supporting Models 27) What is verification and validation? • Verification: