Manual Testing Interview Questions - Part 6

-

In continuation with the latest series of Manual Testing Interview Questions, we present you the part 6 of the course structure. Click on below links for previous parts.


    Manual Testing Interview Questions - Part 6

    • Severity and Priority?
      • Priority
        • “How prior we need to fix the bug is priority.”
        • It means the occurrences of defect.
        • Decide by developer team. 
        • Types(low, medium, high, critical) 
      • SEVERITY
        • “How severe the bug is severity”.
        • It means how bad the defect is and what impact it can cause in our application. 
        • Decide by the testing team. Types(minor, medium, major)
    • What is defect priority?
      • A defect priority is the urgency of the fixing the defect. Normally the defect priority is set on a scale of P0 to P3 with P0 defect having the most urgency to fix.
    •  What is defect severity?
      • Defect severity is the severity of the defect impacting the functionality. Based on the organisation, we can have different levels of defect severity ranging from minor to critical or show stopper
    • Give an example of Low priority-Low severity, Low priority-High severity, High priority-Low severity, High priority-High severity defects.
      • 1. Low priority-Low severity - A spelling mistake in a page not frequently navigated by users. 
      • 2. Low priority-High severity - Application crashing in some very corner case. 
      • 3. High priority-Low severity - Slight change in logo color or spelling mistake in company name. 
      • 4. High priority-High severity - Issue with login functionality.
    • When you install any software how you make sure that software installed correctly? Tell any 5 test cases.
      • First while installation I will check the message at the end which will tell me whether application is successfully installed or not.
      • Then I will go to Installation folder and try to run the Application exe. 
      • Then I will check the icon on desktop or program list.
      • Then I will check the detail of installed application in add/remove program. 
      • Then In the registry I will able to see the entries of this software.
    • Tell me the test cases of door and how to perform integration testing of door? 
      • Functionality:
        • Verify that height & width of the door as per the given specification.  
        • Verify the material used for the door as per the given specification.  
        • Verify the effect of environmental condition on the door.  
        • Verify whether lock attached to door is functioning properly or not. 
        • Verify that fittings of the door is fitted at the desired location 
      • Integration:
        • Verify whether user is able to assemble or dismantle the door from the wall. 
        • Verify whether user is able to assemble or dismantle the lock of the door.  
        • Verify whether user is able to assemble or dismantle the Grip of the door.
      • Performance:
        • Verify whether door is able to sustain the given specified maximum pressure.  
        • Verify whether door is able to sustain the given specified maximum pressure for a longer period of time. 
        • Verify the behavior of door after applying a pressure beyond its specified maximum limit.
      • Usability:
        • Verify the look and feel of the door.  
        • Verify the furniture polish of the door.  
        • Verify the design of the door.
    • What are your considerations while writing down test cases?
      • First I will completely understand the functionality.
      • Then I will start writing down the test cases  
      • While writing down the test cases I will use Black Box Test Case Design Techniques i.e. BVA, Equivalence Partitioning, State Transition Testing along with understanding the Scenarios and use case. 
    • Have you written any test cases without any document like FSD or design document? Do you require updating the initial test case in project life cycle any time?
      • No, I haven’t written any test cases without any documents. But if you know the functionality well then we can write down the test cases. 
      • Yes, most of the time we are getting the CR’s (Change Request) for the given functionality from the business, in that case we are pulling our previous test cases related to that functionality and update it appropriately.
    •  If there are 50 modules in the test plan what will you do? Will you write 50 test plans?
      • Depends. We have a master test plan for entire big project. And for each module we have Module Test Plan. If the entire module we are testing in a similar way then we can write a single module test plan which represents all the 50 Module Test Plan.
    • What is test cases and test plan? Difference between test case and test plan?
      • Test Case is a sequence of keywords or steps used to test the specific feature of an application. While, Test Plan is nothing but Road Map for testing & Test Plan is used for the Planning of Testing Activity

    Comments

    Post a Comment

    Popular posts from this blog

    Azure Tutorials Series - Azure Networking

    -
    Image
    In this article, we will learn about Azure networking concepts such as architecture, microservices, virtual networks, VPNs, subnet, VPN gateways and most importantly Network Security Group(NSG). All these terms are to be understood if you appearing for AZ900 Microsoft Azure Fundamentals exam. Azure Networking In previous articles we have learnt about Micro- services and how they work, these are alos loosely coupled architecture. Some of the features includes Independent components interact with each other with the help of queues Can be updated and deployed independently Highly scalable Supports Asynchronous messaging N-tier Architecture Supports loosely coupled architecture Application divided into multiple tiers such that higher tier can access lower tier but not vice versa Tiers are re-usable and can be updated or replaced easily without any hassle. Three-tier in general Web Tier(front end) Application tier(back end) Data tier(Storage) Virtual Network Isolated network shared by few g
    Read more

    Coforge Interview Questions | Automation Testing profile

    -
    Image
    In this article we will cover recent Coforge Interview questions asked for testing profile.  Date of Interview - 19th December 2020 Mode of Interview - Web conference through TEAMS Interviewer - Rahul Sharma Round - L1 Coforge Interview Questions | Automation testing profile Round L1 Tell me about your project I have been working as a QA for XYZ company from 5.4 years, during this tenure,  I have learnt about Manual testing, Selenium, Database testing, TestNg, framework designing and API testing. What is a webdriver? A webdriver is a an automation framework that allows executing our tests in different browsers. It also supports headless execution using HtmlUnit driver. What are hooks? @Before and @After are called Hooks, they are used before and after any test scenario. How would you like your automation framework to be designed? How can you use data properties in Test NG framework? Explain Access specifiers? Access modifiers define the visibility of the class. There are four different
    Read more

    Testing in CI/CD

    -
    If you are part of testing fraternity you would have heard CI/CD numerous times by now. It's the talk of the software testing town. In this article, we will cover the basics of CI/CD, what actually it is and how it is implemented in software testing. What is continuous integration? In simple terms, development teams can integrate their code into a shared repository. This helps in maintaining code quality and identifying potential issues with the local version of the code at an early stage. What is continuous delivery? Everything that is being continuously merged by the development team, is continuously deployed to the live environment. Continuous delivery is often coined as ‘Continuous Deployment’ as well. Since most developers work in parallel, continuously integrating their code into one repository would mean that the master branch is continuously updated with new features. In order to ensure that there is no compromise in the code quality with so many changes
    Read more