Manual Testing Interview Questions - Part 12

-

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


Manual Testing Interview Questions - Part 12

  • What are the challenges that you faced in your project? Or What are the difficulties You faced in your project.
    • A. The biggest challenge we faced in our current project is to satisfy the customer, as his expectation is too high from all of us. E.g. Customer is expecting to execute more than 50 test cases per day per person. Which is quite difficult as our functionality is very complex. 
    • B. The other challenges we faced is that requirements are changing every often and then without any prior notice or discussion. 
    • C. We are lagging behind the schedule, so every one of us has to stretch hard. So here effort estimation is not correct. 
    • D. We don’t have any defined process. This creates a lot of problem. E.g. Deployment doc is not clear and we are not in sync with the dev people. So in case of any issue while deploying the drops we have to struggle a lot. 
    • E. As a new Team Member for this project, I am facing problem to understand the process, getting domain knowledge, understanding the functionality which is dependent on other functionality. As we don’t have proper Training plan in place. 
  • I have to test an application with 1000 users without any automation tool and time limit is also less. Is this possible? How?
    • It totally depends on the functionality we are going to test. For example if I want to create a Account with 1000 different user, then through UI it is very difficult but I can test this either through back end by running a sql query or at the API level where we are directly passing the required parameter to that function. Here we can take help of scripting language or excel sheet to generate 1000 different users.
  • Tell me how you will perform stress testing of bike?
    • Stress Testing is nothing but testing the application beyond its limit. 
    • So in order to test the bike for Stress Testing:
      • Try to run it at the speed of 10 KM/HR in 4th gear.
      • Try to run it at its highest speed when bike is in 1st gear
      • Try to run it on a very steep road. 
      • Try to run it on a very rocky road where in we can test the shock ups and tyres of the bike.
      • Try to run a bike at highest speed when tyre pressure is very low
      • Try to run when there is no engine oil present etc.
      • Try to run a bike on 1st gear from a very sloppy area here we can check the performance of the gear
  • What are the considerations while writing down the test cases?
    • Before writing down the test cases one should fully understood the functionality, he should be aware that what are we going to test e.g. are we going to test security, functionality, or usability etc. He should be aware of the different test scenario, he should be aware of different test case writing techniques, he should refer the FSD.
  • What is mean by cookies? How to work cookies? Which protocol used for cookies?
    • Cookie is small information stored in text file on user’s hard drive by web server. This information is later used by web browser to retrieve information from that machine. Generally cookie contains personalized user data or information that is used to communicate between different web pages.  
    • HTTP Protocol is used for cookies.
  • How do you decide what to test in the Project?
    • First we have a client meeting where we try to understand what he wants from us. If possible we suggest from our end if he misses something. And then we documented all this things and in test strategy we decide what kind of testing we need to perform by considering customer requirement.
  • What is difference between in inspection, walkthrough, Peer Review and Formal Review?
    • Peer Review: In peer review the code written by one developer or the test cases written by one tester will be reviewed by another developer/tester. It is also called as buddy review. The main purpose of this review is to find out where all the coding standards/Test Cases writing standards follows or not. To find out early defect peer review is important. 
    • Walkthrough: Is a informal type of review where the code written by the developer or Test Cases written by the tester is getting reviewed by a group of 5 to 6 peoples. The owner of the code or Test Cases will present his code/Test Cases and explain them line by line. The Main purpose of walkthrough is to find out the design related issue and any missing things. 
    • Inspection/Formal Review: Is a most formal type of review. A group of 3 to 8 including a moderator, reader, and a recorder to take notes. The main purpose is to find problems and see what's missing, not to fix anything. Participant should be prepares for such type of meetings by reading the document sent by the presenter
  • What should be the Goal of Software Tester?
    • The Goal of a Software Tester should be to find the bug, find them as early as possible and make sure they get fixed. At the same time ensuring that software application meets the entire requirement given in the BRD.
  • Tell me the difference between incremental Testing vs Big Bang Testing?
    • Normally software is developed in multiple pieces called as Module. In Incremental Testing we are testing the software pieces by pieces once all the individual modules are working fine a few of them tested together. Testing combination of pieces of product is called integration testing. And in Big Bang Testing we are testing the application as a whole in one shot 
    • If two modules are working fine independently and after integrating if some error occurs then certainly the problem is in the interface between them. Another benefit of incremental testing is that programmer focuses on each module individually, which probably yields better test coverage
  • What is SRS,FS,BRS?
    • SRS: Software Requirement Specification 
    • FS: Functional Specific 
    • BRS: Business Requirement Specification

 

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