{"id":1440,"date":"2018-06-27T16:10:50","date_gmt":"2018-06-27T16:10:50","guid":{"rendered":"https:\/\/www.h2kinfosys.com\/blog\/?p=1440"},"modified":"2025-03-07T08:24:50","modified_gmt":"2025-03-07T13:24:50","slug":"build-acceptance-testing","status":"publish","type":"post","link":"https:\/\/www.h2kinfosys.com\/blog\/build-acceptance-testing\/","title":{"rendered":"BUILD ACCEPTANCE TESTING"},"content":{"rendered":"<p>The software is tested for readiness before the detailed testing by QA team. It is called as <b>initial level testing<\/b> or <b>build acceptance testing<\/b>. A <b>build<\/b> is a complied code packaged in a single file called as .exe file which can be used for installation of software. It is a superficial testing to check if the pages, links, buttons etc are working. Sometimes, both the terms can be used in different scenarios though there is practically not much difference involved.<\/p>\n<p>The two terms <a href=\"https:\/\/www.h2kinfosys.com\/blog\/100-software-testing-types-set1\/\">initial level testing<\/a> &amp; <a href=\"https:\/\/www.h2kinfosys.com\/blog\/100-software-testing-types\/\">build acceptance testing<\/a> are explained separately below:<\/p>\n<h2><b>INITIAL LEVEL TESTING:<\/b><\/h2>\n<p><b> <\/b>This type of testing is done in the initial stage of application development a set of all tests or procedures based on technical description of the software. Firstly a small piece of code is tested, then fed to the memory. All structural design and code standards are properly determined and calculations for those codes are done and tested with various customers. For example, sometimes the manufacturer is responsible for the design and manufacture of the product. Without his assurance after testing the product is not moved to the next level. So he is the one who tests with the basic level or the manufacturing aspects of the product. Some times this product takes time for giving results.<\/p>\n<h2><b>BUILD VERIFICATION TESTING OR BUILD ACCEPTANCE TESTING:<\/b><\/h2>\n<p><b> <\/b>This type of testing is done to test the integrity of all modules of a software. Integration testing is necessary when many team in a developer team build the modules foe single project. After the project is completed build verification testing is done on every build of a software to check the quality of the product. These tests are done on how to configure and run the software effectively. It is used to check whether all the functionalities are working like it supports for different versions and languages and all menus are integrated properly flags are connected with each file etc. For Example creation of VM\u2019s and server installation setups, database installation setups, test cases are built for creating text editor, writing something on text editor, cut copy functions etc.<\/p>\n<h2><b>Check your understanding:<\/b><\/h2>\n<p>1. Try to identify the differences and similarities between initial level testing &amp; build acceptance testing.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The software is tested for readiness before the detailed testing by QA team. It is called as initial level testing or build acceptance testing. A build is a complied code packaged in a single file called as .exe file which can be used for installation of software. It is a superficial testing to check if [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":7506,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[120,209,121,51],"class_list":["post-1440","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-qa-tutorials","tag-build-acceptance-testing","tag-build-verification-testing","tag-initial-level-testing","tag-software-testing"],"_links":{"self":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/1440","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/comments?post=1440"}],"version-history":[{"count":0,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/1440\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media\/7506"}],"wp:attachment":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media?parent=1440"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/categories?post=1440"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/tags?post=1440"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}