Manual Testing Interview Questions - Part 5

-

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


Manual Testing Interview Questions - Part 5

  • What is defect lifecycle?
  • Defect Life Cycle or Bug Life Cycle is the specific set of states that a Bug goes through from discovery to defect fixation. 
  • Bug Life Cycle phases/status:- The number of states that a defect goes through varies from project to project. Below lifecycle diagram, covers all possible states:
    • New: When a new defect is logged and posted for the first time. It is assigned a status as NEW.
    • Assigned: Once the bug is posted by the tester, the lead of the tester approves the bug and assigns the bug to the developer team.
    • Open: The developer starts analyzing and works on the defect fix.
    • Fixed: When a developer makes a necessary code change and verifies the change, he or she can make bug status as "Fixed." 
    • Pending retest: after fixing the defect the developer gives a particular code for retesting the code to the tester. Here the testing is pending on the testers end, the status assigned is "pending request."
    • Retest: Tester does the retesting of the code at, to check whether the defect is fixed by the developer or not and changes the status to "Re-test."
    • Verified: The tester re-tests the bug after it got fixed by the developer. If there is no bug detected in the software, then the bug is fixed and the status assigned is "verified."
    • Reopen: If the bug persists even after the developer has fixed the bug, the tester changes the status to "reopened". Once again the bug goes through the life cycle. 
    • Closed: If the bug is no longer exists then tester assigns the status "Closed."  
    • Duplicate: If the defect is repeated twice or the defect corresponds to the same concept of the bug, the status is changed to "duplicate."  
    • Rejected: If the developer feels the defect is not a genuine defect then it changes the defect to "rejected."  
    • Deferred: If the present bug is not of a prime priority and if it is expected to get fixed in the next release, then status "Deferred" is assigned to such bugs 
    • Not a bug: If it does not affect the functionality of the application then the status assign to a bug is "Not a bug".
  • How to design test cases? Or tell me different Test Case Design Technique?
    • We are designing the Test Cases using black box type Test Case Design Technique like 
    • State Transition Testing  
    • Boundary Value Analysis 
    • Equivalence Class Partitioning 
    • By using Scenario’s 
    • By using Use Case’s 
    • Pair Wise Testing
  • Tell me about State Transition Testing?
    • Testing the change in state e.g. from on to off, open to close etc. of the application is called as State Transition Testing
  • Tell me about BVA (Boundary Value Analysis)?
    • BVA is a Test Case Design Technique where test cases are selected at the edges of the equivalence class. 
    • For example if one InputBox accept a number from 1 to 1000 then in that case our test cases would be 
      • 1) Test cases with test data exactly as the input boundaries of input domain i.e. values 1 and 1000 in our case. 
      • 2) Test data with values just below the extreme edges of input domains i.e. values 0 and 999. 
      • 3) Test data with values just above the extreme edges of input domain i.e. values 2 and 1001. 
      • 4) Test data with values !@#$#$# and sdf24234 .
  • Tell me about Equivalence Class Partitioning?
    • Equivalence Class partitioning is a Black Box Test Case Design Technique where input data is divided into different equivalence data classes. This method is typically used to reduce the total number test cases to a finite set of testable test cases, still covering maximum requirements. 
    • For example if one InputBox accept a number from 1 to 1000 then Equivalence Class Partitioning in this case is 
      • 1. Class For Accepting Valid input : number from 1 to 1000 
      • 2. Class For Accepting Invalid Input : number <1 or >1000 
      • 3. Class For Accepting Invalid input : entering special characters, alphanumeric value i.e. @#@#@#, blank value etc.
  • Difference between functional specification and requirement specification. Do we need both in orders to write the test cases?
    • Requirement Specification or Business Requirement Document (SRS or BRD) contains all the requirement from the business while FSD is a document which contains list of functionality for the given Requirement. BRD is commonly used by Business People while FSD is used by engineering team. 
    • We are using FSD in order to write down the test cases.
  • IF a>=10 && B<=5 Then some line of code Write down the test case for this?
    • Here we can use Test Case Design Technique to write down the test cases 
      • 1. Test the given line of code when the value of a=10 and B=5 i.e. at the boundary 
      • 2. Test the given line of code when the value of a>10 and b<5 i.e within the boundary 
      • 3. Test the given line of code when the value of a=9 and b=6 i.e. just outside the boundary 
      • 4. Test the given line of code when the value of a=^&% and b=@$@# i.e. checking for invalid invalid input
  • What is entry and exit criteria?
    • ENTRY 
      • It describes when to start testing i.e. what we have to test it should be stable enough to test. 
      • Ex:- if we want to test home page, the SRS/BRD/FRD document & the test cases must be ready and it should be stable enough to test. 
    • EXIT
      • It describes when to stop testing i.e. once everything mentioned below is fulfilled then s/w release is known as exit criteria:- 
        • a. Followed before actually releasing the s/w to client. Checking computer testing is done or not. 
        • b. Documents checking:- test matrix (RTM)/summary reports. 
        • SUSPENSION CRITERIA→ when to stop testing temporarily.
  • What is blocker?
    • A blocker is a bug of high priority and high severity. It prevents or blocks testing of some other major portion of the application as well.
  • MONKEY/AD-HOC TESTING?
    • It is an informal testing performed without a planning or documentation and without having knowledge of the applications/software functionalities. 
    • Monkey testing is a type of testing that is performed randomly without any predefined test cases or test inputs.

    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

    Azure Tutorials Series - IaaS vs PaaS vs SaaS

    -
    Image
    We already have covered Public vs Private vs Hybrid differentiation in the previous article. In this article we will be covering three categories of cloud computing with relevant examples and details. Most of you might already be using these services in your daily day-to-day tasks unaware of the face that your organisation has already started the transition into the cloud. For an example, Office 365 is a active SaaS(Software as a service) that most of us uses, VMs are examples of IaaS(Infrastructure as a service) and Azure SQL Database is PaaS(Platform as a service). Now how do we differentiate between the three categories as a user? Will cover the details below. Infrastructure as a Service(IaaS) Service provider provides you the hardware User gets some control over the hardware, can customise operating system, storage and VMs. Ensuring service is up and running is shared responsibility While cloud provider makes sure that the hardware is functioning correctly, user needs to make sure ...
    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