41 words permalink show parent reply re week 5

This preview shows page 24 - 28 out of 50 pages.

41 words Permalink | Show parent | Reply Re: Week 5 Discussion Question by Zhiyong Cui - Wednesday, 6 March 2019, 2:15 AM Hello Arnoldus: I like your post too in terms of charts and graphs. I think your job is quite like categorized texbook which is very useful for all of us. its super job you have done. thanks for sharing. 39 words Permalink | Show parent | Reply
01.04.2019 CS 2401 - AY2019-T3: Week 5 Discussion Question 25/50 Re: Week 5 Discussion Question by Ntsako Mhlongo - Wednesday, 6 March 2019, 3:27 PM Hello Arnoldus That was an excellent discussion forum post. You really explained everything well and provided us with a great examples. 20 words Permalink | Show parent | Reply Re: Week 5 Discussion Question by Karen by Karen Cristina Cordova - Monday, 4 March 2019, 2:23 PM Why Test Cases? Test cases de²ne exactly what the module should do; Test cases force the designer to think about extreme cases; Test cases force the designer to rethink the module design before constructing it. Unit testing "A unit test is basically the test of the least testable part of a program" (Lima, 2017). The goal is to isolate each part of the system to ensure that it is operating as speci²ed. In this way, the developer who will do the evaluation must always think about what requirements that functionality to be tested has to match, what should be input and output information and also how the ´ow processing of those data works. By using this type of test throughout the implementation it is possible to reduce the number of bugs in the ²nal application. Unit tests work by comparing the results of the functions to be tested with expected values.
01.04.2019 CS 2401 - AY2019-T3: Week 5 Discussion Question 26/50 Figure1.: Test pyramid (Lima, 2017). Answering the proposed question, if I had to choose only three test case design methods to apply during unit testing, they would be: First method) Speci±cation-Based or Black-Box techniques - Decision Table Testing It is a way of expressing, in table form, the set of conditions that are necessary for a set of actions to be executed. The reasons for this choice would be is a method which provides a disciplined way of designing the interaction between conditions and actions in systems; is also a way of verifying redundancy, inconsistency, and non-completeness of projects; and last but not least are concise and standard way of documenting the detailed design of a system. Example: conditions area; actions area; decisions’ rules. conditions decision 1 decision 2 decision 3 decision 4 input 1 - Login valid invalid invalid valid
01.04.2019 CS 2401 - AY2019-T3: Week 5 Discussion Question 27/50 input 2 - Password valid invalid valid invalid actions output 1 – allow access yes no no no Table1.: Example of a decision table test.

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture