Skip to content

Commit 414ffe9

Browse files
authored
V3 (#526)
* refactor: v3 Signed-off-by: Neha Gupta <gneha21@yahoo.in> * refactor: v3 Signed-off-by: Neha Gupta <gneha21@yahoo.in> --------- Signed-off-by: Neha Gupta <gneha21@yahoo.in>
1 parent 1c4b00d commit 414ffe9

File tree

7 files changed

+7
-7
lines changed

7 files changed

+7
-7
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Black-box testing is a software testing method where the tester evaluates the fu
2424

2525
The focus lies solely on examining the software's external behavior, inputs, outputs, and responses to different user actions or system interactions.
2626

27-
![types of testing](../../../../../../../temp/docs/static/img/glossary/types-of-testing.jpeg)
27+
![types of testing](../../../../../static/img/glossary/types-of-testing.jpeg)
2828

2929
## What are the Fundamentals of Black-Box Testing?
3030

versioned_docs/version-3.0.0/concepts/reference/glossary/functional-testing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Functional testing is typically performed by providing the software with input d
2626

2727
<div align="center">
2828

29-
![types of testing](../../../../../../../temp/docs/static/img/glossary/ft.png)
29+
![types of testing](../../../../../static/img/glossary/ft.png)
3030

3131
[Functional Testing](https://keploy.io/blog/community/functional-testing-unveiling-types-and-real-world-applications)
3232

versioned_docs/version-3.0.0/concepts/reference/glossary/grey-box-testing.md

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

2424
**Gray box testing** is a software testing technique that combines aspects of both black box and white box testing. It involves testing the software with partial knowledge of the internal workings of the application. This means the tester has limited access to the internal structures or algorithms, usually at the level of data structures and algorithms but not at the level of the source code itself.
2525

26-
![types of testing](../../../../../../../temp/docs/static/img/glossary/types-of-testing.jpeg)
26+
![types of testing](../../../../../static/img/glossary/types-of-testing.jpeg)
2727

2828
## Why is Gray Box Testing Needed?
2929

versioned_docs/version-3.0.0/concepts/reference/glossary/unit-test-automation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ Keploy offers a one-click unit test generation tool that streamlines the testing
107107
- **Efficiency**: Quickly create unit tests to save time and effort.
108108
- **Enhanced Coverage**: Automatically generate tests for various scenarios, improving code reliability.
109109
- **Focus on Quality**: Spend more time writing high-quality code while ensuring thorough validation.
110-
![Keploy](../../../../../../../temp/docs/static/img/glossary/keploy_VS.png)
110+
![Keploy](../../../../../static/img/glossary/keploy_VS.png)
111111

112112
Get started by downloading the tool from the [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=Keploy.keployio) and boost your development workflow today!
113113

versioned_docs/version-3.0.0/concepts/reference/glossary/white-box-testing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ White box testing, also known as clear box or glass box testing, is a software t
2727

2828
The primary goal of white box testing is to validate the software's internal operations, ensuring that it functions correctly and efficiently. This involves checking all pathways and conditions, optimizing code for speed and performance, and ensuring that there are no hidden errors.
2929

30-
![types of testing](../../../../../../../temp/docs/static/img/glossary/types-of-testing.jpeg)
30+
![types of testing](../../../../../static/img/glossary/types-of-testing.jpeg)
3131

3232
## Fundamentals of White Box Testing
3333

versioned_docs/version-3.0.0/quickstart/nextjs-postgres.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ This will return the response:
8282
curl -X GET http://localhost:3000/api/users
8383
```
8484

85-
![Test Record](../../../../../temp/docs/static/img/nextjs-postgres-record.png)
85+
![Test Record](../../../../../static/img/nextjs-postgres-record.png)
8686

8787
Give yourself a pat on the back! With that simple spell, you've conjured up test cases with a mock! Explore the **Keploy directory** and you'll discover your handiwork in `test-1.yml` and `mocks.yml`.
8888

versioned_docs/version-3.0.0/quickstart/rust-wrap-mongo.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ curl --location 'http://localhost:8000/api/notes/6618fa20875aedcfe96e08ed'
8787
```
8888

8989
This is how keploy terminal would look like:
90-
![Testcase](../../../../../temp/docs/static/img/rust-crud-record.png?raw=true)
90+
![Testcase](../../../../../static/img/glossary/rust-crud-record.png?raw=true)
9191

9292
### Run the testcases
9393

0 commit comments

Comments
 (0)