path: root/tests/functional/README
diff options
authorShwetha Panduranga <>2016-12-16 17:07:42 +0530
committerShwetha Panduranga <>2016-12-16 20:46:48 +0530
commitee1de3dc0eae3d3b1e4cddfbf6eeeec6787b9a31 (patch)
treecb50b9e8c741ea5609975d3de3ddb26526d220ed /tests/functional/README
parent3070312c13e02cace3041d3429b0c31fc10b73ee (diff)
Re-Structuring the directory for more better understanding of test types
Change-Id: I9284eb7ddaf727eef2d107e1e886fc60ec760446 Signed-off-by: Shwetha Panduranga <>
Diffstat (limited to 'tests/functional/README')
1 files changed, 21 insertions, 0 deletions
diff --git a/tests/functional/README b/tests/functional/README
new file mode 100644
index 000000000..07d029dd4
--- /dev/null
+++ b/tests/functional/README
@@ -0,0 +1,21 @@
+Functional Testing:
+ Process of validating that the software conforms to its specifications and
+ correctly performs its required functions.
+ This entails a series of feature by feature validation of behavior using
+ a wide range of normal and erroneous input data.
+ Functional testing divided in 3 categories:
+ - Build Validation tests:
+ Build Verification Test (BVT), also known as Build Acceptance Test,
+ is a set of tests run on each new build of a software to verify that
+ the build is testable before the build is released into further testing.
+ - Smoke Testing:
+ A subset of test cases that are designed to broadly and minimally
+ test to confirm that changes in the code of a particular build
+ function as expected and do not break an entire build.
+ - Regression:
+ Process of retesitng a build after bug fixes and code changes to
+ find any unexpected loss of functionality in the new code base.