Manual Testing Interview Questions - Part 4

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

Manual Testing Interview Questions - Part 4

  • What is white box testing?
    • This also called as glass-box testing, clear-box and structural testing.
    • It is based on applications internal code structure.
    • In this, an internal perspective of the system, as well as programming skills are used to design test cases.
    • In white box testing, the tester analyses the internal architecture of the system as well as the quality of source code on different parameters like code optimization, code coverage, code reusability etc.
    • This testing usually was done at the unit level. 
  • What is black box testing?
    • It is a process of testing a system component considering input, output and general function. 
    • The tester interact with the system through the interface providing input and validating the received output.  
    • It doesn’t require the knowledge of internal program structure.  
    • In this we test UI & backend (coding/database). 
    • External actions are performed.
  • What is positive and negative testing?
    • Positive: 
      • It is determine what system supposed to do.
      • It helps to check whether the application is justifying the requirements or not. 
    • Negative:  
      • It is determine what system not supposed to do. 
      • It helps to find the defects from the s/w.
  • What is gray box testing?
    • It is a combination of both black box and white box testing. The tester who works on this type of testing needs to have access to design documents, this helps to create better test cases.
  • What is test strategy?
    • It is a high-level document and usually developed by project manager. It’s a document which captures the approach on how we go about testing the product and achieve the goals
  • What is test plan?
    • It is a document which contains the plan for all the testing activities
  • What is test scenario?
    • It gives the idea of what we have to test. Or testable part of an application is called TS.
  • What is test case?
    • It is a set of conditions under which tester determines whether an application/ software is working correctly or not
  • What is test bed?
    • An environment configured for testing is called test bed. It consist of hardware, s/w, network configuration.
  • What is test suite?
    • Collection of test cases
  • What is test data?
    • It is a document that is basically used to test the s/w program. It is divided into 2 categories:-
      •  +ve test data which is generally gives to system to generate the expected result. 
      • –ve test data which is used to test the unhandled condition, unexpected , exceptional input condition 
  • How will you ensure that your test cases are complete? Which tool you use to write test cases or do you use simple excel sheets?
    • We are writing down our test cases in excel sheet. And with the help of Requirement Traceability matrix we will ensure that whether all the Requirements have properly covered or not. 
    • And we will perform Peer Test Case Review and Formal Test Case Review to find out the missed test cases which we will add after this review.
  • How many test cases have you developed or executed?
    • On an average for the functionality assigned to me for the given project I have written more than 1000 + test cases. On an average I am executing around 25 to 30 test cases per day.
  • When do you start writing test cases?
    • We start writing down the test cases when we get a FSD i.e. Functional Specification Document.
  • How many Test Cases per day you are going write down in your company?
    • On an average I am going to write down around 50 to 55 test cases per day.

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