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

Popular posts from this blog

Azure Tutorials Series - Azure Networking

Testing in CI/CD

Azure Tutorials Series - IaaS vs PaaS vs SaaS