Manual Testing Interview Questions - Part 13

-

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

Manual Testing Interview Questions - Part 13

    • What is BVT/BAT?
      • Build Verification test is a set of tests run on every new build to verify that build is testable before it is released to test team for further exhaustive testing. These test cases are core functionality test cases that ensure application is stable and can be tested thoroughly. Typically BVT process is automated. If BVT fails that build is again get assigned to developer for fix. 
      • BVT is also called smoke testing or build acceptance testing (BAT) New Build is checked mainly for two things:  
        • Build validation 
        • Build acceptance 
    • How will you perform field validations?
      • I will use Equivalence Class Partitioning and Boundary value analysis in order to perform field validations.
    • What kind of challenges you faced when monitoring the team members?
      • Attitude problems  
      • Conflicts within the team members 
      • Career aspirations are different than what kind of work they are doing now 
      • No out of the box thinking 
      • Frequent Follow up
    • What is function decomposition?
      • Functional Decomposition is a process of splitting a function into different parts in such a way that original function can be reconstructed from these parts. 
      • The main advantage of functional decomposition is that we can get better insight into specific parts of that function. Those parts we can test thoroughly and easily
    • What is your future goal?
      • Short Term Goal: 
        • For exp: 1 to 4 yrs: To become a Lead down the line 2 years. 
        • For exp: 4+: To become a Manager down the line 2 years. 
      • Long Term Goal: To become an entrepreneur down the line 10 yrs.
    • What is one to one, one to many and many to many Relationships in DB? Give example?
      • One to One Relationship: In 1 to 1 relationship, one primary record is associated with 1 related record. For example: 1 Person has only 1 Pan Number. Or 1 student is associated with only 1 division. 
      • One to Many Relationships: In 1 to many relationships, one primary record is associated with multiple related records. For example: 1 Person has many Bank Accounts or 1 student is associated with multiple subjects. Or 1 Purchase order is associated with many line items. Many to Many Relationships: 
      • In Many to Many Relationships, multiple records are associated with multiple related records. For Example: Multiple Sales People are associated with multiple Accounts.
    • When should we go for Load Testing and when should we go for Volume Testing?
      • If we want to test the application with certain amount of data then we should go for volume testing. 
      • For example: How much maximum number of records SQL Server is able to process when number of user is hitting the sql query? 
      • If you want to understand the behavior of the application under a specific expected load without losing the performance, then we should go for load testing. 
      • For Example: How many users are able to perform certain set of operation without affecting the response of time of the application?
    • You are working on a critical release, and we are going to release that product tomorrow and but you have your own personal problem in that case how will you handle such type of scenario?
      • Though I am critical release for that project, I have to have completed my task in any circumstances. What I will do, I will try to finish my personnel problem during first half and will come office a little late and stay till I finish my work else I will assign that ask to my family member and will come to the office and try to finish my task ASAP , as job is on top priority for me.
    • Can we do Load testing manually?
      • No
    • What is product vs project?
      • Product: Developing an application based on global market needs and requirements and no specific client. 
      • Project: Developing a product based on the Client needs or requirements. Project is something that converts an idea or design or a plan in to some concrete entity. 
        • E.g. Construction of a new highway is a project; construction of a software is a project.

    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