Skip to content

Commit 9dd0b10

Browse files
authored
feat: canonical tags and internal links to 2 pages (#877)
* feat: add canonical tags and internal links to regression-testing and black-box-testing glossary pages Signed-off-by: amaan-bhati <amaanbhati49@gmail.com> * feat: add internal blog links and canonical tags to glossary and best-practices pages Signed-off-by: amaan-bhati <amaanbhati49@gmail.com> --------- Signed-off-by: amaan-bhati <amaanbhati49@gmail.com>
1 parent 45df405 commit 9dd0b10

3 files changed

Lines changed: 12 additions & 2 deletions

File tree

versioned_docs/version-4.0.0/concepts/reference/glossary/black-box-testing.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,11 @@ keywords:
1818
- what is black box testing
1919
- keploy
2020
- regression testing
21+
head:
22+
- tag: link
23+
attrs:
24+
rel: canonical
25+
href: https://keploy.io/blog/community/black-box-testing-and-white-box-testing-a-complete-guide
2126
---
2227

2328
Black-box testing is a software testing method where the tester evaluates the functionality of an application without having access to its internal code structure, algorithms, or implementation details. Instead, the tester interacts with the software through its user interface or exposed APIs, treating it as a "black box" whose internal workings are not visible or known.
@@ -30,7 +35,7 @@ The focus lies solely on examining the software's external behavior, inputs, out
3035

3136
This testing approach is essential for several reasons:
3237

33-
- **Independence from Internal Implementation:** Black-box testing allows testers to assess the software's functionality without needing knowledge of its internal workings. This independence ensures that the evaluation remains unbiased and realistic, as it mimics the perspective of end-users who are unaware of the software's internal structure.
38+
- **Independence from Internal Implementation:** [Black-box testing](https://keploy.io/blog/community/black-box-testing-and-white-box-testing-a-complete-guide) allows testers to assess the software's functionality without needing knowledge of its internal workings. This independence ensures that the evaluation remains unbiased and realistic, as it mimics the perspective of end-users who are unaware of the software's internal structure.
3439

3540
- **User-Centric Perspective**: By concentrating on the software's external behavior, black-box testing aligns closely with the user's experience. It helps identify issues that impact user interactions, such as usability flaws, incorrect outputs, or unexpected behaviors, leading to a more user-centric approach to quality assurance.
3641

versioned_docs/version-4.0.0/concepts/reference/glossary/regression-testing.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,11 @@ tags:
88
- Glossary
99
keywords:
1010
- API
11+
head:
12+
- tag: link
13+
attrs:
14+
rel: canonical
15+
href: https://keploy.io/blog/community/regression-testing-an-introductory-guide
1116
---
1217

1318
## What is regression testing?

versioned_docs/version-4.0.0/running-keploy/best-practices-api-testing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ keywords:
2121

2222
## 🛠️ Best Practices in API Testing
2323

24-
API testing ensures the reliability, security, and performance of your application's backend services. To build robust, scalable test suites, here are the best practices you should follow:
24+
[API testing](https://keploy.io/blog/community/what-is-api-testing) ensures the reliability, security, and performance of your application's backend services. To build robust, scalable test suites, here are the best practices you should follow:
2525

2626
### ✅ 1. Define Clear Test Objectives
2727

0 commit comments

Comments
 (0)