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
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.
WHEN DO YOU THINK QA ACTIVITIES SHOULD START
INTEGRATING QA ACTIVITIES AT THE BEGINNING OF THE PROCESS IS ESSENTIAL TO THE SUCCESS OF A PROJECT. IT ENSURES EARLY BUG DETECTING, RISK MANAGEMENT, BETTER DESIGN. IT HELPS NAVIGATE ANY REQUIREMENT AMBIGUITIES AND ULTIMATELY SAVE TIME (AND MONEY) IN THE LONG RUN.
WHAT IS THE DIFFERENCE BETWEEN BUG LEAKAGE AND A BUG RELEASE?
Bug leakage refers to defects that are missed during testing and are only discovered after the software has been released to the customer or end-users
WHILE
Bug release refers to a situation where known bugs or defects are intentionally left in the software when it is released. These bugs are usually documented and communicated to the stakeholders.
Difference between verification and validation?
Verification is about checking if the software conforms to specifications and standards during development.
Validation is about checking if the software meets the needs and requirements of the end-users after development.
Both verification and validation are essential for delivering high-quality software that not only works as intended but also fulfills the user’s needs and expectations.
What tools do you use at your current company
Manual testing: TestRail (testcase management tool), Jira (project management tool)
b. API testing: Postman API
c. Database testing: SQL based database (Microsoft SQL server, Oracle SQL developer)
d. Accessibility testing: Google Lighthouse
e. Automation framework:
i. Selenium – automation tool
ii. IntelliJ – Editor
iii. Java – Coding language
iv. Maven – built tool – integrate dependencies, archives
v. TestNG – testing framework
f. Performance testing – LoadRunner, Jmeter
EXPLAIN THE TESTING LEVELS OR TYPES OF TESTING
THERE ARE FOUR LEVELS OF TESTING.
UNIT TESTING:
IS THE TESTING OF INDIVIDUAL UNITS OR COMPONENTS DONE BY DEVELOPERS TO TEST THAT THE UNIT THEY’VE IMPLEMENTED IS PRODUCING AN EXPECTED RESULT.
INTEGRATION TESTING:
IS A LEVEL OF TESTING THAT WHEN NEW FEATURES ARE BEING INTRODUCED TO THE SYSTEM EVERYTHING WORKS AS IT SHOULD WHEN COMBINED. THE INTERACTION BETWEEN SOFTWARE AND HARDWARE IS TESTED IN INTEGRATION AS WELL
SYSTEM TESTING:
IS DONE BY TESTERS AND IT IS TO TEST THAT WHEN THE SYSTEM IS GIVEN AN INPUT IT SHOULD RESPOND THE WAY IT IS SUPPOSED TO
ACCEPTANCE TESTING:
IS THE END USERS TESTING.
WHAT IS A TEST CASE AND THE COMPONENTS OF ONE
A test case is a set of conditions or variables under which a tester will determine whether an application, software system, or one of its features is working as it was originally established for it to do.
A test case will typically include:
A unique test case ID
A description of the test case
Preconditions for the test
Steps on how to execute the test case
Test data
Expected results for the test case
Actual results for the test case
Status of the test case pass or fail
WHAT TOOLS HAVE YOU USED TO WRITE TEST CASES
I have experience writing test cases with TestLink, and built in tools in Jira such as zephyr
WHAT IS A TEST PLAN
A test plan is a comprehensive document that outlines the strategy, scope, resources, and schedule of intended testing activities. It serves as a blueprint for the testing process, detailing how testing will be conducted, who will perform the testing, what will be tested, and the criteria for success.
A test plan will usually include the following
A good introduction
A list of items to be tested
The scope of the project
Test objectives and criteria
Test environment
the approach
deliverables
Roles and responsibilities
Approval and sign off
WHAT IS A TEST SCENARIO
Test scenarios are high level description of features to be tested. Test scenarios are less detailed than test cases but multiple test case will be made out of a scenario.
I have used trello to create test scenarios
WHAT IS A TEST REPORT
A test report is a document that summarizes the testing activities, results, and findings of a testing phase. It provides a comprehensive overview of what was tested, how it was tested, and the outcomes of those tests. The test report is crucial for stakeholders to understand the quality of the software, the effectiveness of the testing efforts, and any remaining issues or risks
WHAT IS A BUG REPORT
A bug report is a document or an entry in a bug tracking system that describes an issue or defect found in a software application
Key elements:
A unique bud ID
A title/summary
Description of the bug
Steps to reproduce
Expected results
Actual results
Severity
Environment
screen shots/ screen grabs
Status
assignee
How do you approach writing and executing test scripts?
Understanding Requirements – I thoroughly review project documentation, user stories, and acceptance criteria.
Identifying Test Scenarios – I break down the functionality into positive and negative test cases.
Writing Test Cases – I create detailed test scripts, including preconditions, test steps, expected outcomes, and postconditions.
Executing Test Cases – I manually execute tests while logging defects and capturing relevant screenshots/logs.
Regression Testing – I re-run test cases to ensure that fixes do not introduce new defects.
Reporting – I document and report test results, defects, and blockers to the QA manager.
How do you ensure test coverage for a new feature?
identify core functionalities, edge cases, and boundary values.
Consider user workflows and real-world scenarios.
Perform equivalence partitioning and boundary value analysis.
Execute functional, UI, integration, and regression tests.
Collaborate with developers and stakeholders to validate test scenarios.
I also maintain a traceability matrix to ensure all requirements are tested.
What would you do if you encountered a critical defect during testing?
Reproduce the Issue – I verify if the defect is consistent across different test environments and conditions.
Document the Defect – I log detailed defect reports in the test management tool, including steps to reproduce, expected vs. actual results, screenshots, and logs.
Prioritize and Communicate – I immediately inform the QA Manager and development team about the severity and impact of the defect.
Collaborate on Resolution – I work with developers to provide additional details, retest the fix, and ensure no regression issues.
Regression Testing – Once resolved, I execute regression tests to ensure the fix does not introduce new issues.
You are given a very tight deadline to complete testing. How do you prioritize your test cases?
Critical Functionalities – I ensure core features are tested first.
High-Risk Areas – I identify areas with a history of defects or major dependencies.
Smoke Testing – I quickly validate the stability of the build before deeper testing.
Regression Testing – I run high-priority regression tests to catch major issues.
Bug Fix Verification – I validate fixes to prevent reopening issues.
If necessary, I coordinate with the QA Manager to adjust test scope while maintaining quality.
How do you handle a situation where developers reject a bug you reported?
Review the Bug Report – I double-check if the defect is well-documented with clear steps, logs, and expected vs. actual results.
Gather Supporting Evidence – I provide additional details like screenshots, video recordings, or logs to prove the issue.
Discuss with the Developer – I have a collaborative discussion to understand their perspective and clarify the issue.
Check Requirements – I verify project documentation to validate whether the behavior aligns with expected functionality.
Escalate if Necessary – If the disagreement persists, I escalate to the QA Manager or Business Analyst for further review.
Do you have experience with test management tools? Which ones have you used?
Yes! I have experience using JIRA, TestRail, and qTest for test management. I use these tools to:
Create and manage test cases.
Log and track defects.
Link test cases to user stories for traceability.
Generate test execution reports for stakeholders.
Have you worked with SharePoint Online or legal application testing before? (Nice-to-have qualification)
I have not worked extensively with SharePoint Online or legal applications, but I am eager to learn. Given my experience in manual testing, test planning, and defect tracking, I can quickly adapt and gain expertise in new domains by reviewing documentation, collaborating with subject matter experts, and hands-on testing.
TELL US ABOUT A BUG YOU FOUND THAT YOU WERE PROUD OF
The Bug
During one of my exploratory testing sessions, I discovered an issue where applying multiple discount codes in a specific sequence would incorrectly calculate the total discount, leading to a significantly higher discount than intended. This was a major issue because it could result in substantial financial losses and affect the integrity of our pricing model.
Discovery Process
To pinpoint the problem, I began by reproducing the bug consistently in a controlled environment. I meticulously documented each step and noted that the issue occurred only when certain types of discount codes were combined. I then used debugging tools to trace the application’s behavior and discovered that the discount calculation algorithm had a flaw when handling overlapping discount rules.
Resolution
I documented the bug in our tracking system with detailed steps to reproduce, screenshots, and logs. I then collaborated with the development team to provide additional insights from my testing. Together, we modified the discount calculation logic to ensure that it accurately applied discounts without overlap. I also designed and implemented new test cases to cover various combinations of discount codes to prevent similar issues in the future.
How do you stay up to date with the latest QA trends and best practices?
I stay updated by:
Taking online QA courses (e.g., Udemy, LinkedIn Learning).
Participating in QA forums and LinkedIn groups.
Attending webinars and conferences focused on software testing.
Reading blogs like Ministry of Testing and TestGuild.
Practicing hands-on testing with new tools and techniques.
Why do you want to work at (here)?
I am excited about the opportunity at Qualitest Group because:
It is a leader in quality assurance and software testing.
The role aligns with my experience in manual testing and test script execution.
I appreciate the emphasis on independent work while collaborating with teams.
I am eager to contribute my skills and grow within a company that values quality and innovation.
I look forward to the opportunity to bring my attention to detail, problem-solving skills, and testing expertise to your team!
Do you have any questions for us?
What are the biggest quality assurance challenges your team is currently facing?
How does the QA team collaborate with development in your Agile setup?
What excites you about working here
