6) What is client/server application?
Ans: It has limited number of users and runs on two or more devices.
7) What is web-based application?
Ans: It has unlimited number of users and runs on two or more devices. It’s a URL driven.
8) Why do we test software?
Ans: To identify areas of weakness,
To establish the degree of quality,
To make sure requirements have been met,
To provide an understanding of the overall system,
9) What is software quality?
Ans: Quality software is bug-free, within budget, meets requirements and expectations, delivered on time and it’s maintainable.
11) What is GUI?
Ans: GUI stands for Graphical User Interface. GUI is multiple options and selections.
12) What is software testing?
Ans:
13) What is SDLC?
Ans: SDLC stands for Software Development Life Cycle. SDLC is the entire process of formal, logical steps taken to develop a software product.
14) What are the phases of SDLC?
Ans: (1) Planning
(2) Analysis
(3) Design
(4) Development Production
(5) Testing
(6) Deployment
(7) Maintenance
15) What is planning in SDLC?
Ans: The planning phase determines a solid plan for developing an information system. It defines the system to be developed, set the project scope, and makes a schedule Plan that defines what, when and who questions of software development activities.
16) What is analysis in SDLC?
Ans: Primary activity of this phase is to gather business requirements. End users and IT specialists work together to gather document and understand the business requirements. Once all the business requirements are defined, end users approve all the requirements and sign them off.
17) What is design in SDLC?
Ans: It is used to build a technical blueprint of how the The proposed system will work.
18) What is development in SDLC?
Ans: Developers take all the detailed design documents from design phase and transform them into an actual system.
19)What is testing in SDLC?
Ans: The testing phase of the SDLC verifies that the system works properly and meets all the business requirements. First, we developed detailed test conditions then we actually perform the test.
20)What is deployment in SDLC?
Ans:
21) What is maintenance in SDLC?
Ans: Gather information from customers and upgrade the system and make sure it continues to meet the business goal.
22) What are the development methodologies in SDLC?
Ans: Waterfall Development Methodology V-Development Methodology and Agile
23) What is the waterfall model?
Ans: It’s a sequential development methodology.
29) What is agile?
Ans: Agile is an iterative/incremental development methodology.
30) What are the advantage and disadvantage of agile?
Ans: Advantage:
i) Developers can work together and more productive approach.
ii) Easy to interact with a team.
Disadvantage:
Hard to build a regulated application.
Hard to maintain the original scope of the process.
31) What is a sprint?
Ans: It’s a time frame, agile developers take 2-4 weeks to complete on iteration or build.
32) What are the software testing methodologies?
Ans: Black box testing , White box testing
33) What is black box testing?
Ans: Testing applications without knowing the internal code, logic or the application.
34) What is white box testing?
Ans: Testing internal code or login of an application.
35) What is functional testing?
Ans: Testing application interface or function of an application to make sure the application or interface functions as expected.
36) What are the types of functions?
Ans: Edit box, button, link, sub-link, drop-down menu, check box.
37) What is regression testing?
Ans: Re-testing after any modification, change or addition in an application to make the sure modification, change or addition does not create any error in the application.
38) What is system testing?
Ans: It is end-to-end testing. Testing an entire system to make sure. front-end, back-end, and connected devices are working together.
What is database testing?
Ans: Testing back-end or database to make sure data is correct or valid, and data is available in the back-end database.
39) What is UAT testing?
Ans: UAT stands for User Acceptance Testing. Testing an application or system to make sure application or system meets user expectation.
41) What is smoke testing/sanity testing/operational testing?
Ans: Testing application main function without any formal plan or procedure to make sure application is operational.
42) What is integration testing in black box?
Ans: Testing more than one module(s) or component(s) of an application to make sure the module(s) or component(s) are working.
43) What is unit testing in white box?
Ans: Testing a piece of code or component of code to make sure code or logic is working as expected.
44) What is integration testing in white box?
Ans: Testing more than one unit or piece of code to make sure the units are working together.
45) What is STLC?
Ans: STLC stands for Software Testing Life Cycle. STLC is the process uses to verify applications or software or system.
46) What are the processes of testing?
47) What is requirement?
Ans: Requirement means what you want from a system or software and what shall the software or system do.
48) What is a good requirement?
Ans: Good requirement is unique, precise, complete, bounded, consistent, and testable.
What is BRS/BRD?
Ans: BRS stands for Business Requirement Specification. It contains a high level of requirement of customer that is to be developed as software or system.
What is URS?
Ans: URS stands for User Requirement Specification. URS is
an essential document which outline precisely what the user (or customer) is expecting from the system.
51) What is SRS?
Ans: SRS stands for System Requirement Specification. SRS is implemented form of BRS. It contains details requirements for software, hardware and database. SRS contains functional and non-functional requirement.
52) What is FRS?
Ans: FRS stands for Functional Requirement Specification. Document provides more detail information. It contains technical information and data needed to design the application.
53) What is functional requirement?
Ans: It always has user interaction.
54) What is non-functional requirement?
Ans: It has no user interaction or involvement.
55) How would you review and analyze requirement?
Ans:We make sure it’s inconsistency and ambiguity. It does not have any formatting, grammatical or logical error.
56) What is use case?
Ans:
57) How do you write use case?
Ans:
58) What is test plan?
Ans: Test plan is document that includes object of testing, scope of testing, assumption, test entry criteria, test exit criteria, risk, test pass/fail criteria, and test deliverable.
59)What is a good system or software?
Ans:
60) What is test case?
Ans: It’s a document that includes input, output, expected value or result, and steps necessary to execute a test.
61) Why do we write test cases?
Ans: To test or verify requirements and to test software or system.
62) What is RTM?
Ans: RTM stands for Requirement Traceability Matrix. RTM is a document that shows tracing or mapping between requirement and test case.
63) Why RTM?
Ans: Shows if any requirement does not cover in testing.
64) What is ALM?
Ans: ALM stands for Application Lifecycle Management. It’s a web-based application life cycle management system, and it’s a web-based repository central storage that store data.
65. What can you do with ALM?
Ans: ALM can manage project tasks or activities, report or track project status.
Manage Requirement (Business Analyst)
Manage Testing (Software Test Engineer/QA)
Create Report (Business Owner, End User)
69) What is JIRA?
Ans: JIRA is a defect-tracking or reporting tool. We can write user stories and maintain project issues or tasks.
70) What is benefit of JIRA?
Ans: It’s a user-friendly tool and web-based.
71) What is database?
Ans: Database is an organized collection of data. A structured set of data held in a computer.
72) How do you design a database?
Ans: Identify entity, relation between entity and attributes of an entity.
73) What is variable?
Ans: Variable is a name that can hold information, or variable is place holder.
74) How did you write test cases?
Answer: I have written test cases based on Business and Functional requirements Documents.
75) Can you please explain the situation where you don’t have any requirement document? How did you build your test cases?
Answer: In my QA career, I have faced the situation where there were no Business or Functional requirements, in that type of case I had to speak with BA (Business Analyst) or developer to understand the application functionality and try to come up with test cases.
76) Can you please explain QA/Testing process from your previous experience?
Answer: In my last project our testing process start with writing Test Plan, then developing test cases based on requirements, preparing RTM, Test data, and environment, then execute test cases finding defects, log defect in ALM, after the defect is fixed retesting the defect and provide signoff.
77) What is the difference between Test Plan and Test
Strategy?
Answer: A test plan is a document that describes objectives, scope, approach, and focus of a software testing effort.
Test Strategy is a set of guidelines that describes test design.
Test plan is specific to each project and Test Strategy can be company/organization level.
78) Did you write a test plan? What should be included in the test plan?
Answer: Yes, in my last project I have written a test plan and in the test plan I usually include Introduction, Application Details, Features to be tested, Features not to be tested, Test techniques, Testing Cycle, Test environment, Entry/Exit Criteria, Test Deliverables, Assumption and Dependencies, Responsibilities, Schedule.
79) Can you explain to me the defect life cycle?
Answer: Sure. Once I find a defect and I retest a few times to see if that defect is reproducible then I log the defect in ALM. By default, the defect status is new, once the developer review and accept the defect the status changes from new to open. Once defect is fixed then developer changes the defect to fixed. Then I had to retest the defect and if it is working as expected I close the defect or if it is not working then I reopen the defect.
80) How did you overcome the situation when you have disagreement with developer about any defect?
Answer: I had this experience in my last project where I had disagreement with developer with one of the defects where developer is unable to reproduce the defect and notified me this is not a defect. I sat with developer and assisted to reproduce the defect.
81)What is the difference between verification and validation?
Answer: Verification ensures the product is designed to deliver all functionality to the customer. It is making sure all the functionality exists in the application as per requirement and Validation typically involves actual testing and takes place after verifications are completed. Making sure the expected resultmatches with the actual result.
82. What is the difference between QA and QC?
Answer: The difference between QA and QC is QA is Process-oriented and QC is product Oriented.
83. If you do not understand any requirement, whom should you contact?
Answer: If I don’t understand any requirement my first point of contact would be Business Analyst since he/she is responsible for creating the Business Requirement Document.
84) If you have very high level BRD how do you write test cases from there?
Answer: In my QA career I had a situation where BRD doesn’t have application details or very high level. In this type of situation, I usually communicate with BA or Developer to understand the application flow of execution to better understand the high-level Business Requirements and develop my test cases.
85) Can you explain the process how code gets pushed to production?
Answer: Sure. In my last project we had 4 different environments.
Dev/QA/Stage/Production. Once developers finished with their coding and complete the unit test, they pushed the code to QA environment. Once the build is in QA environment, I perform all type of testing and provide signoff once all test cases are executed successfully and there are no major defects. Then the build gets pushed to stage environment for different groups/Stake holder so they can quickly look at the changes or new feature. Once it is approved the code gets pushed to production.
86) Can you please explain the architecture of our last project?
Answer: (Depends on your project).
87) Which environment you perform testing?
Answer: Usually I perform my testing in QA environment but sometimes to assist developer I had to perform testing in Dev environment.
88) Who pushes the code to QA Environment?
Answer: In my last project Developer pushes the code in different environment.
89) What is your involvement in Agile Process?
Answer: Sure. My involvement in Agile process start with Spring Analysis/Planning Meeting where we do a grooming session and Product owner select the stories from product backlog and explain the stories to the team and I had to make sure those stories are testable and If I have any question.
Everyday day in the morning we had Daily Standup/DailyScrum where I have provided a quick status: What I have doneyesterday, what I am planning to do today and if I am facing any problem.
During the spring development I have written test cases, execute test cases, find defect, log defect, and retest the defect after fix. Then we had showcase where product owner review the completed feature with stakeholder and I just participate in that meeting.
And we finished each sprint with Sprint Retrospective meeting where I participate and provide my feedback what worked well in the sprint, what didn’t work well and how we can improve in future sprint.
91) Give me an example from your last project where you have to perform Regression and Integration testing?
Answer: (Depends on your project)
92) Have you performed End to End testing? Give an example.
Answer: Answer is depending on your project.
93) What information you include when you log a defect?
Answer: Once I find defect, I logged that defect in QC/ALM and I include following information: Defect Summary, Steps to Reproduce, Test Data, Environment, Priority/ Severity, Screen Shot, Test Cycle, Build Version, Assigned To.
94) How did you set the Priority and Severity? Can you please provide an example?
Answer: Based on the urgency of fixing the defect I set the Priority and degree of negative impact on the quality of the software I set the severity. However, we used to have defect management meeting every week where product owner and developer review the defect with QA team and defect priority/severity get finalize during that time.
96) What do you do when you cannot proceed further with your testing?
Answer: When I am unable to proceed further with my testing, I immediately log a defect in QC with high priority and informed the development team that QA is on hold until that defect is resolve.
97) What is your approach when application cannot be launch?
Answer: If it is a web-based application, usually I check internet connection then I have to make sure also if Web Server or app server is running by using ping command. If Servers are up and running then I usually remote log into the server and check error log file.
98) Have you ever had a situation where you have found a defect that is not in the requirement?
Answer: Yes, I have had this experience before where I have found a defect and that’s not in the requirement. Usually, I logged that defect and bring it to BA and Product owner attention. Once requirement is finalized then I develop a test cases for that requirement.
99) Given the situation please provide your best answer:
“You have 100 test cases and you were given 2 weeks to execute and manager decided to cut the timeline to 1 week”. How many test cases you will execute and which test cases you will select?
Answer: In this type of situation I will perform high priority test cases if priority is not set for each test case then only positive test cases of core functionality can be executed to make sure features are working. For example: if I have a requirement “Valid user are able to login to system” and I have written positive and negative test cases to satisfy this requirement and QA doesn’t have enough time to perform all test cases. I can execute only positive test cases which will satisfy this business requirement.
101) How do you select test cases for Regression Suite?
Answer: I select my regression test cases sub set of test cases from initial suite based on these 3 criteria: a) ensure the core functionality works b) bugs found have been resolved. C) Potential to detect errors for application features changes.
102) What is your strength? What is your weakness?
Answer: [Based on Job Description]
103) Have you performed Backend Testing? How did you do it in your last project? Please explain?
Answer: Yes. I have performed data validation by writing SQL query using SQL Developer tool. Where I connect to database and if necessary, join multiple tables to retrieve data and validate against front end or other source.
104) When do you know you have performed enough testing?
Answer: When all my test cases have been executed successfully and there are no outstanding major or critical defects.
105) When do you provide QA signoff?
Answer: In my last project QA exit criteria was when there is no major or critical outstanding defect that time, I provide my signoff.
106) What do you do, when you find a defect?
Answer: Once I find a defect, I execute the test case few times to make sure the defect is reproducible. Then I logged that defect into QC/ALM.
107) Have you ever worked on Mobile Application?
Answer: Yes. I have used Simulator and real device to perform manual and usability testing on mobile application. Also, I have used perfecto mobile which is UFT add in to automate manual mobile test scenarios.
108) If you have web-based application to test. How do you go about testing it? What is the process?
Answer: First of all, I will perform functional test to make sure all the functionality is working properly then integration or end to end test but I will make sure to perform compatibility or cross browser testing since this a web-based application.
109)How would you ensure that you have covered 100% testing?
Answer: Usually I develop RTM (Requirement Traceability Matrix) which maps between requirement and test cases. This way I can ensure that for each requirement at least I have written one test case.
110) What type of problems you have faced in the past? How did you solve it?
Answer: In my last project, while working in agile environment I have face these challenges where requirements were changing frequently and I had to update my test cases and test scripts. Therefore, I had to put some extra hours and sometimes work in the weekend too to accommodate the QA timeline.
111) Do you have experience in Compatibility Testing? How did you perform Compatibility testing?
Answer: Yes, I have performed compatibility testing before. In my last company we had a QA lab where each machine was set up with different OS and Browser. Also, I have used browser stack tool where each browser is installed in different VM machine.
112) What do you do when developer doesn’t accept the defect you have discovered?
Answer: First of all, I will find out why the defect is not acceptable by developer. Is it developer cannot reproduce the defect or requirement understanding issue? If it is reproducible issue, I can always assist developer to reproduce the defect and if it is requirement related issue then I can bring it to BA or Product owner attention so they can clarify the requirement.
113) Give me few problems that happen during Application Development?
Answer: In my career, I have experienced following problems with Application development: requirements are not clearly defined; last minute requirements need to change for business reason and doesn’t provide enough time for testing.
114) What if the software is so buggy it cannot be tested at all?
Answer: If my smoke test is not passed successfully then we refuse the build and let the developer know immediately.
115) What if there is not enough time for thorough testing? What will be your approach?
Answer: I will execute only high-priority test cases.
116) What can be done (QA Perspective) if requirements are changing continuously?
Answer: We need to have process in place so stakeholder can approve the requirement before the sprint begins and once sprint is starting the scope is locked down.
117) Have you ever performed Adhoc Testing?
Answer: I have performed Adhoc testing mainly with the aim of trying to uncover defects or flaws which cannot be captured through traditional or formal processes followed during the testing cycle. I didn’t follow any particular test case or test scenario when perform ad-hoc testing.
118) Please describe a situation where you had to communicate directly with different groups within a company?
Answer: For Defect related issue I have communicated with development team, for requirement question I had to communicate with BA, product owner.
119. What is the MAIN benefit of designing tests early in the life cycle?
Ans: It helps prevent defects from being introduced into the code.
120. What is risk-based testing?
Ans: Risk-based testing is the term used for an approach to creating a test strategy that is based on prioritizing tests by risk. The basis of the approach is a detailed risk analysis and prioritizing of risks by risk level. Tests to address each risk are then specified, starting with the highest risk first.
121) A wholesaler sells printer cartridges. The minimum order quantity is 5. There is a 20% discount for orders of 100 or more printer cartridges. You have been asked to prepare test cases using various values for the number of printer cartridges ordered.
122. Which of the following groups contain three test inputs that would be generated using Boundary Value Analysis?
Ans: 4, 5, 99
123) What is the purpose of exit criteria?
Ans: The purpose of exit criteria is to define when a test level is completed.
124) What determines the level of risk?
Ans: The likelihood of an adverse event and the impact of the event determine the level of risk.
125) What is the MAIN objective when reviewing a software deliverable?
Ans: To identify defects in any software work product.
126. What is functional system testing?
Ans: Testing the end to end functionality of the system as a whole is defined as a functional system testing.
127. What are the benefits of Independent Testing?
Ans: Independent testers are unbiased and identify different defects at the same time.
137) Which activity in the fundamental test process includes evaluation of the testability of the requirements and system?
Ans: A ‘Test Analysis’ and ‘Design’ includes evaluation of the testability of the requirements and system.
138) What is typically the MOST important reason to use risk to drive testing efforts?
Ans: Because testing everything is not feasible.
139) What is random/monkey testing? When it is used?
Ans: Random testing often known as monkey testing. In such type of testing data is generated randomly often using a tool or automated mechanism. With this randomly generated input the
system is tested and results are analyzed accordingly. Thesetesting are less reliable; hence it is normally used by the beginners and to see whether the system will hold up under adverse effects.
140. What is an equivalence partition (also known as an equivalence class)?
Ans: An input or output ranges of values such that only one value in the range becomes a test case.
141. When should configuration management procedures be implemented?
Ans: During test planning.
142. A Type of functional Testing, which investigates the functions relating to detection of threats, such as virus from malicious outsiders?
Ans: Security Testing
143. Testing wherein we subject the target of the test, to varying workloads to measure and evaluate the performance behaviors and ability of the target and of the test to continue to function properly under these different workloads?
Ans: Load Testing
কোন মন্তব্য নেই:
একটি মন্তব্য পোস্ট করুন