Manual Testing Interview Questions - Part 9

-

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


Manual Testing Interview Questions - Part 9

      •  If developer rejects the bug then what should you do? Give the 5 reason of defect rejection? If you found bug and developer said that this bug is not reproducible at his place then what you will do?
        • If Developer rejects a bug and if it’s really a bug I will attached the references of FSD and error snapshot which will give him correct understanding of that bug. 
        • If he still doesn’t agree on that I will arrange a live meeting with him and reproduced this issue in front of him. 
        • If still he don’t agree on that and saying this is the problem with your environment then I will escalate it to my Manager. 
        • Developer can rejects Issues …… 
          • 1. If it is an Environmental issue. 
          • 2. If the functionality is out of scope. 
          • 3. If the logged defect is as per design spec. 
          • 4. If the logged defect is unable to reproduce 
          • 5. If the logged defect is not able to fix due to technical limitation 
          • 6. If the logged defect is postponed till next release
      • What are the different types of Bugs we normally see in any of the Project?
        • Bugs related to functionality  
        • Bugs related to missing requirement  
        • Bugs in the FSD/BRD  
        • Usability related bugs  
        • Bugs related to performance e.g. Application is very slow 
        • Bugs occurred at the boundary value  
        • Bugs in the developed code etc
      • What are the contents in defect reporting? or What are different field in your bug defect life cycle?
        • Contents in defect tracking tools are  
          • Title of the Bug  
          • Severity  
          • Priority  
          • Found & Fixed in Build  
          • Description of the Bug  
          • Attachment  
          • State  
          • Reason  
          • Created By  
          • Creation Date etc.  
          • Application Name
      • If you found bug then how you will conclude that this is bug?
        • When I found a bug first I will try to reproduce it on my machine 2 or 3 times. Then I will cross verify the same issue on different machines having same drop. At the same time I will confirm it by cross verifying the Functional Specification Document.
      • If you found any bug then what is your next step?
        • Once I found a bug then I will first ensure that whether it’s a really bug or not? And at the same time I will ensure that has any one already logged it or not? Then I will log that issue in Bug tracking tool/Defect tracking tool(DTT).
      • How you decide severity and priority?
        • S1 is assigned if the bug will cause a system crash or data loss.  
        • S2 is assigned if the bug will cause major functionality or other severe problems.  
        • S3 is assigned if the bug will cause minor functionality problems. 
        • S4 is assigned if the bug is the cause of unclear wording or error messages in low visibility fields. 
        • Priority 1 – Crash, Data Loss, Unrecoverable Error, or Ship Stopping issue.  
        • Priority 2 – Critical issue. May or may not be critical for release, but is a severe problem.  
        • Priority 3 – Minor issue, affects less than 5% of users, edge/corner case. A workaround may exist.
      • Tell me the latest bug which you found recently? Or Client appreciations for any bugs? Interesting bugs you logged
        • In our application on Home Page we are showing the number of vendors deleted. But when I verified at the back end it was actually not deleted but was marked for deletion. So I logged this issue having S3 and Priority P2.
      • Can duplicate bug reassign?
        • Ideally we should not reassign the duplicate bug. But if you reassign it nothing will happen, only dev will see 2 similar bugs in his bucket and reject one of them.
      • If there is no company Logo on web page what will be the Severity and Priority for this?
        • Severity of this bug is S3 and Priority of the Bug is P1. As it is not affecting the functionality the severity of the bug is S3 but Company Logo is a like a Brand symbol for that company so the Priority of the bug is P1.
      • What is Risk Analysis?
        • Risk Analysis is a process of Identification of risk under different conditions, finding out cause-&-effect relationship between probable happenings. How we can reduce that risk along with privative measures.

      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

      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

      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