Update Manual Testing Processes (#2540)
ChuckD3ath
2 years ago
committed by
GitHub
parent
dcb0e3a843
commit
97cec3a5ec
5 changed files with 25 additions and 7 deletions
@ -1,3 +1,6 @@ |
|||||||
# TDD - Test Driven Development |
# TDD - Test Driven Development |
||||||
|
|
||||||
The team needs to adopt TDD; developing against tests and use-cases. With this approach, you can assure the minimum amount of time and effort being consumed during regression rounds. Having a clear set of acceptance criteria can make the team more productive in a shorter time. |
Test Driven Development (TDD) is software development approach in which test cases are developed to specify and validate what the code will do. In simple terms, test cases for each functionality are created and tested first and if the test fails then the new code is written in order to pass the test and making code simple and bug-free. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.guru99.com/test-driven-development.html'>What is Test Driven Development (TDD)? Tutorial with Example</BadgeLink> |
||||||
@ -1,3 +1,6 @@ |
|||||||
# Test Planning |
# Test Planning |
||||||
|
|
||||||
i.e. how we are trying to test, what is the scope of the delivery and the followed strategy. |
A Test Plan is a detailed document that describes the test strategy, objectives, schedule, estimation, deliverables, and resources required to perform testing for a software product. Test Plan helps us determine the effort needed to validate the quality of the application under test. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.guru99.com/what-everybody-ought-to-know-about-test-planing.html'>Test Plan: What is, How to Create (with Example)</BadgeLink> |
||||||
@ -1,3 +1,9 @@ |
|||||||
# Test Cases and Scenarios |
# Test Cases and Scenarios |
||||||
|
|
||||||
Test cases and scenarios creation is the best of all software testing activities. Based on clearly written and documented test cases you can cover all the possibilities and release with more confidence. |
A Test Case is a set of actions executed to verify a particular feature or functionality of your software application. A Test Case contains test steps, test data, precondition, and postcondition developed for a specific test scenario to verify any requirement. The test case includes specific variables or conditions, using which a testing engineer can compare expected and actual results to determine whether a software product is functioning as per the requirements of the customer. |
||||||
|
|
||||||
|
A Test Scenario is defined as any functionality that can be tested. It is a collective set of test cases which helps the testing team to determine the positive and negative characteristics of the project. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.guru99.com/test-case-vs-test-scenario.html'>Test Case vs Test Scenario – Difference Between Them</BadgeLink> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.guru99.com/test-case.html'>How to Write Test Cases in Software Testing with Examples</BadgeLink> |
||||||
@ -1,3 +1,6 @@ |
|||||||
# Compatibility |
# Compatibility |
||||||
|
|
||||||
A QA Engineer is a simulation for many users - you should be able to simulate different usre's behaviors, capabilities whether it is hardware or software components. |
Compatibility is nothing but the capability of existing or living together. Compatibility Testing is a type of Software testing to check whether your software is capable of running on different hardware, operating systems, applications, network environments or Mobile devices. |
||||||
|
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.guru99.com/compatibility-testing.html'>What is Compatibility Testing? Forward & Backward Example</BadgeLink> |
||||||
@ -1,6 +1,9 @@ |
|||||||
# Verification and Validation |
# Verification and Validation |
||||||
|
|
||||||
Understand the difference between Verification and Validation and understand when and what to apply. |
Verification in Software Testing is a process of checking documents, design, code, and program in order to check if the software has been built according to the requirements or not. The main goal of verification process is to ensure quality of software application, design, architecture etc. The verification process involves activities like reviews, walk-throughs and inspection. |
||||||
|
|
||||||
- **Verification:** Are we building the product in the right way? |
Validation in Software Engineering is a dynamic mechanism of testing and validating if the software product actually meets the exact needs of the customer or not. The process helps to ensure that the software fulfills the desired use in an appropriate environment. The validation process involves activities like unit testing, integration testing, system testing and user acceptance testing. |
||||||
- **Validation:** Are we building the right product? |
|
||||||
|
<ResourceGroupTitle>Free Content</ResourceGroupTitle> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.guru99.com/verification-v-s-validation-in-a-software-testing.html'>Differences Between Verification and Validation</BadgeLink> |
||||||
|
<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.guru99.com/design-verification-process.html'>Design Verification & Validation Process</BadgeLink> |
||||||
Loading…
Reference in new issue