{"id":361,"date":"2022-05-16T17:27:57","date_gmt":"2022-05-16T16:27:57","guid":{"rendered":"https:\/\/blogs.glowscotland.org.uk\/glowblogs\/phsn5computingscience\/?page_id=361"},"modified":"2024-12-05T14:39:19","modified_gmt":"2024-12-05T14:39:19","slug":"testing","status":"publish","type":"page","link":"https:\/\/blogs.glowscotland.org.uk\/glowblogs\/phsn5computingscience\/testing\/","title":{"rendered":"Testing"},"content":{"rendered":"

Once the program has been written it is necessary to test\u00a0the program for any errors. The testing stage can take\u00a0quite a long time as the program must work under most\u00a0conditions.\u00a0\u200b<\/p>\n

There are three types of testing:\u00a0\u200b<\/p>\n

Normal<\/strong>\u00a0(N) – Data the program should expect to handle.\u00a0\u200b<\/p>\n

Extreme<\/strong>\u00a0(L) – Data at the limits of what the program should\u00a0handle.\u00a0\u200b<\/p>\n

Exceptional<\/strong> (E) – Data which the program should not handle<\/p>\n

The aim of testing is to prevent software failure. Using normal, exceptional and extreme test data as part of a test plan will reduce the prevalence of syntax, logic and execution to errors in code.<\/p>\n

Test Tables<\/h2>\n

Test tables are used to provide a structure to testing.<\/p>\n

Programmers will often create a table with a selection of normal, extreme and exceptional data that they intend to use during testing. The table will include:<\/p>\n

    \n
  • a column for the expected result<\/li>\n
  • a column for what actually happens when the program runs<\/li>\n<\/ul>\n

    The programmer will refer to the functional requirements created at the analysis phase to act as a reminder of the inputs that the program is expected to handle.<\/p>\n

    What data to test<\/h3>\n

    A test table should include:<\/p>\n

      \n
    • at least two items of normal data<\/li>\n
    • at least two items of exceptional data]<\/li>\n
    • both extreme values if testing a range of numbers<\/li>\n<\/ul>\n

      It is also good practice to test the values immediately out with the accepted range as it is common to find errors that occur because of a selection statement that makes use of incorrect logical operators.<\/p>\n

      \"\"<\/p>\n

      Syntax, Execution and Logic errors<\/h2>\n

      There are three types of error that you need to understand.<\/span><\/p>\n

      Syntax error<\/h3>\n

      The rule of the code is not being met, such as incorrect spelling, forgetting to include commas\/speech marks. A syntax error will be identified by an interpreter and will stop the code when the error is found..<\/span><\/p>\n

      Execution error<\/h3>\n

      Sometimes called a runtime error, execution errors only become evident during run time. An execution error occurs when a program is asked to do something that it cannot, resulting in a \u2018crash\u2019. The widely used example of a run time error is asking a program to divide by 0.<\/span><\/p>\n

      Logic error<\/h3>\n

      The program will run, but the outputs will be wrong due to an incorrect calculation or using <<\/strong> instead of ><\/strong> or AND<\/strong> rather than OR<\/strong>.<\/p>\n

       <\/p>\n","protected":false},"excerpt":{"rendered":"

      Once the program has been written it is necessary to test\u00a0the program for any errors. The testing stage can take\u00a0quite a long time as the program must work under most\u00a0conditions.\u00a0\u200b There are three types of testing:\u00a0\u200b Normal\u00a0(N) – Data the program should expect to handle.\u00a0\u200b Extreme\u00a0(L) – Data at the limits of what the program […]<\/p>\n","protected":false},"author":79984,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-361","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/blogs.glowscotland.org.uk\/glowblogs\/phsn5computingscience\/wp-json\/wp\/v2\/pages\/361","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.glowscotland.org.uk\/glowblogs\/phsn5computingscience\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/blogs.glowscotland.org.uk\/glowblogs\/phsn5computingscience\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.glowscotland.org.uk\/glowblogs\/phsn5computingscience\/wp-json\/wp\/v2\/users\/79984"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.glowscotland.org.uk\/glowblogs\/phsn5computingscience\/wp-json\/wp\/v2\/comments?post=361"}],"version-history":[{"count":5,"href":"https:\/\/blogs.glowscotland.org.uk\/glowblogs\/phsn5computingscience\/wp-json\/wp\/v2\/pages\/361\/revisions"}],"predecessor-version":[{"id":615,"href":"https:\/\/blogs.glowscotland.org.uk\/glowblogs\/phsn5computingscience\/wp-json\/wp\/v2\/pages\/361\/revisions\/615"}],"wp:attachment":[{"href":"https:\/\/blogs.glowscotland.org.uk\/glowblogs\/phsn5computingscience\/wp-json\/wp\/v2\/media?parent=361"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}