Manual Testing Questions Flashcards
What is the difference between functional testing and non-functional testing?
Functional testing verifies that the application works as expected based on requirements (e.g., login functionality, data validation).
Non-functional testing evaluates system performance, security, usability, and reliability (e.g., load testing, accessibility testing).
Explain the difference between black-box testing and white-box testing.
Black-box testing focuses on testing software functionality without knowing its internal code structure.
White-box testing involves testing internal structures, logic, and code paths to ensure proper implementation.
What is the significance of boundary value analysis in test case design?
Boundary Value Analysis (BVA) helps identify errors at boundary limits, where bugs are more likely to occur.
Example: If an input field accepts values from 1-100, test cases should include 0, 1, 100, and 101.
Can you explain the concept of test case prioritization? How would you do it?
Test case prioritization helps execute critical test cases first, ensuring faster defect detection.
Prioritization is based on factors like business impact, high-risk areas, and frequently used functionalities.
Describe the various stages of the Software Development Life Cycle (SDLC). Where does testing fit in?
SDLC stages: Requirement Analysis → Design → Development → Testing → Deployment → Maintenance
Testing is integrated after development and is also performed iteratively in Agile methodologies.
How do you identify and report bugs? What’s your process for managing defects?
Identify issues through test execution and log them in a defect tracking tool (e.g., JIRA).
Provide details: Steps to reproduce, expected vs. actual results, severity, priority, and screenshots.
Work with developers to verify and retest fixes before closing defects.
What is the difference between severity and priority in bug reporting?
Severity: Impact of the defect on functionality (e.g., critical crash vs. minor UI issue).
Priority: How soon the bug needs to be fixed (e.g., a typo in a company logo might have high priority but low severity).
What is Regression Testing, and why is it necessary in Agile environments?
Regression testing ensures new changes haven’t broken existing functionality.
Agile environments require frequent regression testing due to continuous updates.
What is smoke testing, and when would you perform it?
Smoke testing is a quick, high-level test to check whether the critical functionalities of an application work after a new build.
Performed before detailed testing to determine if the build is stable.
Can you explain what a test plan is and what are the key components of it?
A test plan outlines the testing scope, approach, resources, and schedule.
Key components: Test objectives, scope, test environment, test deliverables, risks, and timelines.
How do you ensure the test cases you write cover all the requirements?
Trace test cases back to requirements using a Requirement Traceability Matrix (RTM) to ensure full coverage.
Explain Exploratory Testing. When would you use it, and how does it differ from scripted testing?
Exploratory testing is unscripted testing where testers explore the application dynamically.
Useful when requirements are unclear or in early testing stages.
Scripted testing follows predefined test cases.
How do you deal with ambiguous requirements when creating test cases?
Seek clarification from stakeholders or business analysts.
Use exploratory testing to identify possible issues.
Document assumptions and validate them with the team.
What is the difference between system testing and integration testing?
System testing verifies the entire application as a whole.
Integration testing checks interactions between different modules or systems.
How would you handle situations where you find conflicting test results?
Reproduce the issue in a controlled environment.
Compare results with expected behavior and consult with developers.
Use logs, screenshots, and debugging tools for further analysis.
What do you understand by the term “Test Environment”? What does it include?
The test environment is a setup that mimics the production system for testing.
Includes hardware, software, databases, test data, and network configurations.
What is the role of the tester in Agile methodology?
Work closely with developers, participate in daily stand-ups, refine requirements, and test incrementally within sprints.
How do you handle situations when there are unclear or vague requirements in Agile sprints?
Engage with the product owner or business analyst to clarify.
Collaborate with the team to define acceptance criteria.
Explain how you handle changes in the test scope during the testing phase.
Assess the impact of changes on existing test cases.
Adjust test coverage accordingly and re-prioritize test execution.
Can you describe the process of test closure? What activities are part of this phase?
Test closure involves finalizing testing activities and delivering test summary reports.
Activities include defect analysis, documentation of lessons learned, and project sign-off.
Briefly describe yourself, elaborating on your qualifications and experience (don’t menmtion internship)
I have an educational background in both web development and manual/automation testing. I have over 3 years experience in testing and that includes creating test documentation, such as test plans, test scenarios, test cases, RTM, defect reports. I have an in depth understanding of the STLC SDLC and DLC, and i’d like to conclude by saying i’m ready to take on the challenges and contribute to the success of the team.
WHAT ARE YOUR TASKS AND RESPONSIBILITIES ON A DAILY BASIS
ATTENDING VARIOUS MEETINGS, ANALYZING REQUIREMENTS, CREATING, EXECUTING , AND REPORTING TEST CASES, CREATING BUG REPORTS AND WORKING WITH DEVELOPERS TO FINDING SOLUTIONS TO THE ROOT CAUSES OF THEM, AND FINDING AUTOMATION CANDIDATES TO CONVERT INTO AUTOMATION TEST SCRIPTS.
WHAT TYPE OF SOFTWARE TESTING ARE YOU PERFORMING AT YOUR CURRENT POSITION
DATABASE, AUTOMATION, API TESTING, INTEGRATION, REGRESSION, SMOKE, BLACKBOX TESTING, UTA TESTING, PERFORMANCE USING LOAD RUNNER, SOME ACCESSIBILITY TESTING,
CAN YOU TELL US ABOUT THE BUG LIFECYCLE
MANAGEMENT IS A VITAL PHASE OF THE SOFTWARE TESTING LIFECYCLE. AS A QA IT HAS BEEN AN INTEGRAL PART OF THE TESTING PROCESS IN MOST OF MY PROJECTS.
WHEN AN ERROR IS FOUND THE STATUS IS SET TO NEW AND THEN ASSIGNED TO A DEVELOPER. AFTER BEING ASSIGNED A DEV CAN EITHER ACCEPT OR REJECT THE BUG OR DEFER IT . IF ACCEPTED THE DEVELOPER WILL WORK ON IT AND THE BUG WILL BE IN PROCESS AND THEN EVENTUALLY FIXED. ONCE FIXED WE RETEST AND VERIFY THAT IT HAS INDEED BEEN FIXED AND IF IT HAS WE CAN CLOSE IT OUT. IF THE ISSUE IS STILL THERE THE BUG GETS REOPENED AND ASSIGNED BACK TO A DEVELOPER AND STARTS THE PROCESS OVER AGAIN.
