From 8ced2e607daeb64b861b6eeb2ae2ea3f3e3d60cb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nagy=20Gerg=C5=91?= <32914217+Geryke18@users.noreply.github.com> Date: Sat, 24 Sep 2022 14:02:17 +0200 Subject: [PATCH] Update 102-black-box-testing.md (#1853) Based on white box testing --- .../102-testing-approaches/102-black-box-testing.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/content/roadmaps/113-qa/content/100-qa-basics/102-testing-approaches/102-black-box-testing.md b/content/roadmaps/113-qa/content/100-qa-basics/102-testing-approaches/102-black-box-testing.md index 045a76292..7668f9e78 100644 --- a/content/roadmaps/113-qa/content/100-qa-basics/102-testing-approaches/102-black-box-testing.md +++ b/content/roadmaps/113-qa/content/100-qa-basics/102-testing-approaches/102-black-box-testing.md @@ -1 +1,6 @@ -# Black box testing \ No newline at end of file +# Black box testing + +Black Box Testing is a software testing method in which the functionalities of software applications are tested without having knowledge of internal code structure, implementation details and internal paths. Black Box Testing mainly focuses on input and output of software applications and it is entirely based on software requirements and specifications. It is also known as Behavioral Testing. + +Free Content +What is BLACK Box Testing? Techniques, Example & Types