Manual Testing Interview Questions - Part 11

-

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


Manual Testing Interview Questions - Part 11

    •  How will you test the application without having any requirements?
      • We will perform exploratory testing. Means we will first explore that application and then test. We can explore that application by taking the help of superiors who is having knowledge about that application, or by going to help files of that application or by understanding the domain for which this product belongs etc.
    • Did you get any bug which was not in the requirement or in ad-hoc testing (which was not in the test case)? Or did you get any bug in Ad-hoc testing? Explain
      • Yes. In our application on the home page first we were showing all the accounts but later on it was creating a performance issue when number of accounts was more than 100. Then I logged a bug saying that paging functionality and search functionality should be provided to navigate to and to find out the specific account. Earlier it was not mentioned in the Requirement documents
    • Explain memory leak with example?
      • Memory leak is nothing but unintentional consumptions of memory. Most of the Application when we closed gets invisible from the desktop running in the backend.
      • Unintentional memory consumption by a computer program where the program fails to release Memory when no longer needed.
    • You have only 4 line of requirements how you will test it?
      • I will try to split that requirement into functionality first. Then I will try to create user scenarios and write down test cases on that and will test it.
    • What is Web Testing? What is the Thing we need to consider for Testing Web Based Applications?
      • Web Testing is nothing but testing the Web Based Application. We need to consider:  
        • Functionality 
        • Usability  
        • Performance 
        • Security  
        • Server Side Interface  
        • Client Side Compatibility while performing web based application.
    • What is difference between Integration and Incremental Integration testing?
      • Integration Testing is nothing but testing the interface between different components or modules.
      • After performing integration testing of all the modules if any new functionality is added into that application then we can integrate it with our application and perform the integration testing called as incremental integration testing.
    • Difference between System Testing and System Integration Testing?
      • In system testing we are testing the functional as well as non functional aspects i.e. Security, Performance, Installation, Up gradation, etc of the application. While in System Integration Testing we perform the integration of existing system with another system. E.g. Integration of two or more systems with each other.
    • Tell me who is responsible for Unit Testing either developer or tester?
      • For any testing related activity Tester is responsible. So ideally speaking Tester is responsible for unit testing. But practically speaking most of the testers are not aware of development languages so developer is performing unit testing.
    • What is Traceability matrix? What are Forward Traceability and Reverse Traceability?
      • Traceability Matrix is used to mapped your:  
        • Requirement with Test Cases or  
        • Functionality with Test Cases or  
        • Requirement with Defects or  
        • Functionality with Defects or 
        • Forward Traceability matrix helps you to provide information about how many test cases you have written for a given requirement/functionality. Or how many bugs we have logged for a given requirement/functionality. 
        • Reverse Traceability matrix helps you to provide information about; this given test case belongs to which requirement/functionality. Or this logged bug belongs to which requirement/functionality
    • What is traceability Matrix? And when and who is preparing it?
      • Traceability Matrix is used to mapped your:  
        • Requirement with Test Cases or  
        • Functionality with Test Cases or 
        • Requirement with Defects or  
        • Functionality with Defects or 
        • When we start writing down test cases for a given functionality or requirement, test lead prepares this requirement traceability matrix. 

    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