Suggested Certification for Manual Testing

ISTQB Certification, CAST Certified Associate In Software Testing, Quality Assurance Institute - CSTE

Recommended Book 1 for Manual Testing

★★★★☆
Check Amazon for current price
View Deal
On Amazon

Recommended Book 2 for Manual Testing

★★★★☆
Check Amazon for current price
View Deal
On Amazon

Recommended Book 3 for Manual Testing

★★★★☆
Check Amazon for current price
View Deal
On Amazon

Recommended Book 4 for Manual Testing

★★★★☆
Check Amazon for current price
View Deal
On Amazon

Recommended Book 5 for Manual Testing

★★★★☆
Check Amazon for current price
View Deal
On Amazon

Note: *Check out these useful books! As an Amazon Associate I earn from qualifying purchases.

Interview Questions and Answers

Verification checks if the software is built according to the specifications (Are we building the product right?). Validation checks if the software meets the users needs (Are we building the right product?).

The STLC is a sequence of activities conducted by testers to ensure software quality. Common phases include: Requirements Analysis, Test Planning, Test Case Development, Test Environment Setup, Test Execution, and Test Closure.

The different levels of testing are: Unit Testing, Integration Testing, System Testing, and Acceptance Testing.

Priority refers to the urgency with which a bug needs to be fixed. Common priority levels include: Immediate, High, Medium, and Low.

Common techniques include: Equivalence Partitioning, Boundary Value Analysis, Decision Table Testing, and State Transition Testing.

Equivalence partitioning is a testing technique that divides the input data into groups (partitions) where the software is expected to behave similarly.

Boundary value analysis is a testing technique that focuses on testing the input values at the boundaries of the input domain.

Key skills include: Strong analytical and problem-solving skills, attention to detail, good communication skills, knowledge of testing methodologies, and domain knowledge.

Regression testing is a type of testing performed after code changes to ensure that existing functionality has not been negatively impacted.

Exploratory testing is a testing approach where testers dynamically design and execute tests based on their knowledge and experience, learning about the software as they go.

A test case is a document that describes the steps to be performed to verify a specific feature or functionality of the software.

A test plan is a document that outlines the scope, objectives, resources, and schedule for the testing process.

A bug report is a document that describes a defect found in the software, including details on how to reproduce the issue and its severity.

Severity refers to the impact of a bug on the softwares functionality. Common severity levels include: Critical, High, Medium, and Low.

Advantages include: Suitable for exploratory and usability testing, cost-effective for small projects, human observation can identify subtle issues missed by automation, and easy to implement.

Disadvantages include: Time-consuming, prone to human error, not suitable for large or complex projects, and can be expensive in the long run.

Types include: Unit Testing, Integration Testing, System Testing, User Acceptance Testing (UAT), Black Box Testing, White Box Testing, Regression Testing, and Exploratory Testing.

Black box testing is a testing technique that focuses on testing the functionality of the software without knowing the internal code structure or implementation details.

White box testing is a testing technique that involves testing the internal code structure and implementation details of the software.

Manual testing is a software testing process in which test cases are executed manually by a tester without using any automation tools. The tester analyzes the software, identifies potential issues, and reports them to the development team.

Testing ensures effective and high performance, functionality of the product. Product testing guarantees reliability, stability, security, and customer satisfaction.

Test Case is a set of actions executed to verify particular feature or functionality, it includes test steps, data, expected results for testing  whereas Test Scenario is any functionality that can be tested and it is testing of end to end functionality.

Present day software applications are so complex, and run in interdependent environment, that full testing is impossible. The following are some of the most common things to consider when considering when to stop: Testing Deadlines, Completion execution

- In manual tests, humans may observe, judge, and contribute insight, which is useful when it comes to user-friendliness or a rich consumer experience.
- When usability and flexibility is being tested.
- Manual testing proves useful when the test

4 levels - unit testing, integration testing, system testing, and acceptance testing.

A Test Automation Framework is a set of guidelines that includes things like coding standards, test data processing, and object repository treatment, among other things.

Agile Testing can begin at the start of the project with continuous integration between development and testing. Agile testing is software testing that follows the best practices of Agile development.

Linear Scripting.

- The Test Library Architecture Framework.

- The Data-Driven Testing Framework.

- The Keyword-Driven or Table-Driven Testing Framework.

- The Hybrid Test Automation Framework.

The bug lifetime begins when a tester reports a bug and concludes when a tester determines that the issue has been resolved and will not recur.

With a valid username and password, the user will be able to log in.

- With a legitimate username and an invalid password, a user cannot log in.

- When the form is blank and the Submit button is hit, proper alert message is displayed.
<

Every new build undergoes a series of build verification testing to ensure that it is testable before being released to the testing team for further testing.

Read and comprehend the documentation/guides for the software project.

- Create test cases that cover all of the documentation's requirements.

- With the help of the Team Lead and the Client, review and baseline the test cases

Boundary value analysis is testing the boundaries between partitions. It is a technique where the input data is divided into partitions of valid and invalid values.

Test scripts are a line-by-line description of the system transactions that must be performed in order to validate the application or system.

SDLC - Software Development Life Cycle.

STLC -Software Testing Life Cycle.

bug - Bug is a failure or flaw in a software program that produces undesired or incorrect results.

defect - Defect is an error in c

BUGZILLA.

- P ALM.

- JIRA (developed by Atlassian)

- Mantis.

- Trac.

- Redmine.

- FogBugz.

- YouTrack.

Defect_ID

- Defect Description

- Detailed description of the Defect

- Version

Validation is the process of checking whether the software product captures the customer's needs and is up to the mark, while verification is the process of checking that the software achieves its goal without any bugs.

TestCaseId.

- Test Summary.

- Description.

- Prerequisite or pre-condition.

Quality control can be described as part of quality management that is focused on fulfilling quality requirements. While quality assurance relates to how a process is performed or how a product is made.

Explain with examples that sync with the job description.

Model–view–controller(MVC) is a software design pattern used for developing user interfaces that separate the related program logic into three interconnected elements. Each of these components is built to handle specific development aspects of an applicat

Explain specific instances with respect to the job JD.

Explain specific instances with respect to the job JD.

A good software engineer is someone who is not only competent to write code but also competent to create, produce and ship useful software.

The primary aim of the code review is to ensure that the codebase overall product quality is maintained over time. It helps give a fresh set of eyes to identify bugs and simple coding errors. All of the tools and processes of code review are designed to t

Use a phased life-cycle plan, Continuous validation, Maintain product control, Use the latest programming practices, Maintain clear accountability for results.

Software engineering always requires a fair amount of teamwork. The code needs to be understood by designers, developers, other coders, testers, team members and the entire IT team.

Schedule, Quality, Cost, Stakeholder Satisfaction, Performance

The most common software sizing methodology has been counting the lines of code written in the application source. Another approach is to do Functional Size Measurement, to express the functionality size as a number by performing Function point analysis.

The major parts to project estimation are effort estimation, cost estimation, resource estimate. In estimation, there are many methods used as best practices in project management such as-Analogous estimation, Parametric estimation, Delphi process, 3 Poin

software configuration management (SCM) is the task of tracking and controlling changes in the software code, part of the larger cross-disciplinary field of configuration management. Whereas change management deals with identification, impact analysis, d

Basecamp, Teamwork Projects, ProofHub, Zoho Projects, Nifty, Trello, JIRA, Asana, Podio, etc.

A feasibility study is a study that takes into account all of the related factors of a project — including economic, technological, legal, and scheduling considerations — to assess the probability of completing the project.