Basic Interview Questions for Manual Testing. What is the difference between Functional. Requirement and Non- Functional Requirement? The Functional Requirement specifies how the system or application SHOULD DO. Non Functional Requirement it specifies how the system or application SHOULD.
MANUAL TESTING INTERVIEW QUESTIONS AND ANSWERS 1. What are the components of an SRS? An SRS contains the following basic components: Introduction. 101+ Manual and Automation Software Testing Interview Questions and Answers. What is Business Requirement Document (BRD)? What information a tester need to provide while generating Test Cases? What is System Requirement Document?
Manual testing interview questions and answers - What is baseline testing?, What is benchmark testing?, What is verification and validation?, Explain Branch Coverage.
BE. Some functional Requirements are. Authentication. Business rules. Historical Data. Legal and Regulatory Requirements. External Interfaces. Some Non- Functional Requirements are. Performance. Reliability. Security Recovery.
Data Integrity. Usability. How Severity and Priority are related to. Severity- tells the seriousness/depth of the bug where as Priority- tells which bug should rectify first. Severity- Application point of view. Priority- User point of view 3. Explain the different types of Severity?
User Interface Defect- Low. Boundary Related Defects- Medium. Error Handling Defects- Medium.
- What makes a good test engineer? A good test engineer has a 'test to break' attitude, an ability to take the point of view of the customer, a strong desire.
- 6684+ Manual Testing interview questions and answers for freshers and experienced. Manual Testing technical job interview questions of various companies and by job.
- What is 'configuration management'? Configuration management covers the processes used to control, coordinate, and track: code, requirements, documentation.
Calculation Defects- High. Interpreting Data Defects- High.
Hardware Failures& Problems- High. Compatibility and Intersystem defects- High. Control Flow defects- High. Load conditions (Memory leakages under load testing)- High. What is the difference between Priority.
Severity? The terms Priority and Severity are used in Bug Tracking to share the. Severity: Is found in the Application point of view.
Priority- Is found in the User point of. Severity- (tells the seriousness/depth of the bug)The Severity status is used to explain how badly the deviation is affecting the build. The severity type is defined by the tester based on the written test cases and functionality. Example. If an application or a web page crashes when a. PRIORITY- (tells which bug should. The Priority status is set by the tester to the developer mentioning the time frame to fix a defect. If High priority is mentioned then the developer has to fix it at the earliest.
The priority status is set based on the customer requirements. Example If the company name is misspelled in the home. Severity: Describes the bug in terms of functionality. Priority: Describes the bug in terms of customer.
Few examples: High Severity and Low Priority. Application doesn't allow customer expected configuration. High Severity and High Priority - > Application doesn't allow multiple. Low Severity and High Priority - > No error message to prevent wrong. Low Severity and low Priority - > Error message is having complex meaning. Or. Few examples: High Severity - Low priority.
Supposing, you try the wildest or the weirdest. The priority would be low as the. Low Severity - High priority. An example would be- you find a spelling. Say, the name is. Google and its spelled there as 'Gaogle'. Though, it doesn't.
Hence, the priority is high. High severity- High Priority. A bug which is a show stopper. An example would be a run time. Low severity - low priority. Cosmetic bugs. What is Defect Severity? A defect is a product anomaly or flaw, which is.
The classification of defect based. Defect Severity. 5. What is Bucket Testing? Bucket testing (also known as A/B Testing) is mostly used to study the impact of. What is Entry and Exit Criteria in Software Testing?
Entry Criteria is the process that must be present when a system begins, like, SRS (Software Requirement Specification) FRS (Functional Requirement Specification) Usecase Test Case Test plan. Exit Criteria ensures whether testing is.
Test Summary Report. Metrics. Defect Analysis report. What is Concurrency Testing? Concurrency Testing (also commonly known as Multi User Testing) is used to know. Application, Code Module or Database by different. It helps in identifying and measuring the problems in.
Response time, levels of locking and deadlocking in the application. Example. Load runner is widely used for this type of. Vugen (Virtual User Generator) is used to add the number of concurrent. Gradual Ramp up or Spike Stepped.
Explain Statement coverage/Code coverage/Line Coverage? Statement Coverage or Code Coverage or Line Coverage is a metric used in White. Box Testing where we can identify the statements executed and where the code is.
In this process each and every line of the code. Some advantages of Statement Coverage / Code. Coverage / Line Coverage are. It verifies what the written code is expected to do and not to do. It measures the quality of code written. It checks the flow of different paths in the program also ensure whether those paths are tested or not. To Calculate Statement Coverage,Statement Coverage = Statements Tested / Total.
No. of Statements. Explain Branch Coverage/Decision Coverage?
Branch Coverage or Decision Coverage metric is used to check the volume of. This process is used to ensure whether all the.
To Calculate Branch Coverage,Branch Coverage = Tested Decision Outcomes /. Total Decision Outcomes.
What is the difference between High level and Low Level test case? High level Test cases are those which cover major functionality in the. Low level test cases are those related to User Interface (UI) in the. Explain Localization testing with example? Localization is the process of changing or modifying an application to a. This includes change in user interface, graphical.
In terms of Localization Testing it verifies how correctly the application is. In case of translation required of the application on that local language. Other. formats like date conversion, hardware and software usage like operating system.
Examples for Localization Testing are. In Islamic Banking all the transactions and. Shariah Law, some important points to be noted in. Islamic Banking are.
In Islamic Banking, the bank shares the profit and loss with the customer. In Islamic Banking, the bank cannot charge interest on the customer; instead they charge a nominal fee which is termed as "Profit. In Islamic Banking, the bank will not deal or invest in business like Gambling, Alcohol, Pork, etc.
In this case, we need to test whether these Islamic banking conditions were. In Islamic Lending, they follow both the Gregorian calendar and Hijiri Calendar.
The Hijiri Calendar is commonly. Islamic Calendar followed in all the Muslim countries according to the. The Hijiri Calendar has 1.
Gregorian calendar. In this case, we need to test the repayment. Gregorian calendar and Hijiri Calendar. Explain Risk Analysis in Software Testing? In Software Testing, Risk Analysis is the process of identifying risks in.
In Software testing some unavoidable risk might takes place like. Change in requirements or Incomplete requirements. Time allocation for testing. Developers delaying to deliver the build for testing. Urgency from client for delivery.
Defect Leakage due to application size or complexity. To overcome these risks, the following activities can be done. Conducting Risk Assessment review meeting with the development team. Profile for Risk coverage is created by mentioning the importance of each area. Using maximum resources to work on High Risk areas like allocating more testers for High risk areas and minimum resources for Medium and Low risk areas. Creation of Risk assessment database for future maintenance and management review.
What is the difference between Two Tier. Architecture and Three Tier Architecture? In Two Tier Architecture or Client/Server Architecture two layers like. Client and Server is involved. The Client sends request to Server and the Server. The problem with the Two. Tier Architecture is the server cannot respond to multiple requests at the same.
The Client/Server Testing involves testing the Two Tier Architecture of user. Client. Hardware and Servers. In Three Tier Architecture or Multi Tier Architecture three layers like. Client, Server and Database are involved. In this the Client sends a request to. Server, where the Server sends the request to Database for data, based on that.
Database sends back the data to Server and from Server the data is. Client. The Web Application Testing involves testing the Three Tier Architecture. User interface, Functionality, Performance, Compatibility. Security and Database testing. What is the difference between Static testing and dynamic testing? Static Testing(done in Verification stage)Static Testing is a White Box testing technique.
Code Reviews, Inspections, Walkthroughs are. Dynamic Testing(done in Validation stage)Dynamic Testing is done by executing the actual. Examples of Dynamic. Testing methodologies are Unit Testing, Integration Testing, System Testing and. Acceptance Testing. Some differences between Static Testing and Dynamic Testing are,Static Testing is more cost effective than Dynamic Testing because Static Testing is done in the initial stage.
In terms of Statement Coverage, the Static Testing covers more areas than Dynamic Testing in shorter time. Static Testing is done before the code deployment where the Dynamic Testing is done after the code deployment. Static Testing is done in the Verification stage where the Dynamic Testing is done in the Validation stage. Explain Use case diagram. What are the. attributes of use cases? Use Case Diagrams is an overview graphical representation of the functionality.
It is used in the analysis phase of a project to specify the system. In Use Case Diagrams the whole system is defined as ACTORS, USE CASES and.
ASSOCIATIONS, the ACTORS are the external part of the system like users. USECASES is the behavior or functionality of the. ACTORS perform an action, the ASSOCIATIONS are the line drawn. ACTORS and USECASES. One ACTOR can link too many. USECASES and one USECASE can link too many ACTORS. What is Web Application testing?
Explain the different phases in Web. Application testing? Web Application testing is done on a website to check its load, performance. Security, Functionality, Interface, compatibility and other usability related. In Web application testing, three phases of testing is done, they are,Web Tier Testing. In Web tier testing, the browser compatibility.
IE, Fire Fox and other web browsers. Middle Tier Testing. In Middle tier testing, the functionality and. Database Tier Testing. In Database tier testing, the database.
Explain Unit testing, Interface Testing and Integration testing.