Manual Testing Interview Questions - Part 10

-

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


Manual Testing Interview Questions - Part 10

  • What is GUI testing?
    • GUI Testing is nothing but testing the product or application that uses Graphical User Interface, to ensure that it meets the customer requirement.
  • What is Security Testing?
    • Security Testing is nothing but to test how well the system protects against unauthorized internal and external access, willful damage etc. In security testing we are finding out the vulnerabilities of the application
  • What is Stress Testing?
    • Stress Testing is nothing but to test the software beyond its limit. Stress Testing are of two types: 
      • By Keeping the H/W resources constant and increasing the load of the user.  
      • By keeping the load of the user constant and gradually decreasing the H/W resources. 
      • E.g. to test the software using Low Ram, Low Hard Disk, Low CPU etc.
  • What is Load Testing?
    • Load Testing is nothing but to test the software at its limit. Load testing is mainly performed to find out how much maximum user application can handle without losing the performance.
  • What is Soak Testing or Endurance Testing?
    • To Test the Software at its limit for a longer period of time e.g. for more than 2 days. The main purpose of Endurance Testing to check the behavior of application if it is under heavy load for a longer period of time.
  • What is the difference between Load and Stress Testing?
    • In Load testing we are testing the software at its maximum limit. The basic purpose of Load testing to find out how many maximum user applications can handle without losing the performance. 
    • But in Stress Testing we are testing the software beyond its limit to check the behavior of application when it crosses the maximum limit of user.
  • Tell me the difference between functional and system testing?
    •  In Functional Testing we are testing the functionality of the application while 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 along with functionality
  • What is mean by Ad-hoc testing and exploratory testing? Or what is the difference between Ad-hoc testing and Smoke testing?
    • Exploratory testing is nothing but testing the application without having requirements. So here in Exploratory testing first we explore the application and then test. 
    • Ad-hoc means we know our final target but don’t know how to reach to that target. So Ad-hoc testing is nothing but to test the application with the intention of finding the bugs. This type of testing is carried out without any test cases or test plan.  
    • Smoke Testing is nothing but testing the main-main functionality of the application to ensure that nothing has been affected and we can go for further exhaustive testing.
  • What is Requirement Understanding Document (RUD)?
    • When analyst gathers the requirement from the customer, he prepares a document where he puts all the requirements told by the customer, we called this document as Requirement Understanding document. By going through this document customer gets the confidence whether analyst properly understood his requirement or not?
  • Explain the testing cycle you will follow if you have 100 test cases in the first cycle... 25 failed and 75 passed. How many test cases you will pick for the second cycle?
    • I will pick all the 100 Test Cases in second cycle, to ensure that there should not be any side effect of fixing the bugs on other functionality.

         

        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