CSE306 Software Quality in Practice Dr. Carl Alphonce - - PowerPoint PPT Presentation

▶
cse306 software quality in practice
SMART_READER_LITE
LIVE PREVIEW

CSE306 Software Quality in Practice Dr. Carl Alphonce - - PowerPoint PPT Presentation

Dec 09, 2023 715 likes •1.01k views

CSE306 Software Quality in Practice Dr. Carl Alphonce alphonce@buffalo.edu 343 Davis Hall Recall the rules 1. Understand the requirements 2. Make it fail 3. Simplify the test case 4. Read the right error message 5. Check the plug 6.

slide-1
SLIDE 1

CSE306 Software Quality in Practice

  • Dr. Carl Alphonce

alphonce@buffalo.edu 343 Davis Hall

slide-2
SLIDE 2

Recall the rules

1. Understand the requirements 2. Make it fail 3. Simplify the test case

  • 4. Read the right error message

5. Check the plug 6. Separate fact from fiction 7. Divide and conquer 8. Match the tool to the bug 9. One change at a time

  • 10. Keep an audit trail
  • 11. Get a fresh view
  • 12. If you didn’

t fix it, it ain’ t fixed

  • 13. Cover your bug fix with a regression test
slide-3
SLIDE 3

Recall the rules

1. Understand the requirements 2. Make it fail 3. Simplify the test case

  • 4. Read the right error message

5. Check the plug 6. Separate fact from fiction 7. Divide and conquer 8. Match the tool to the bug 9. One change at a time

  • 10. Keep an audit trail
  • 11. Get a fresh view
  • 12. If you didn’

t fix it, it ain’ t fixed

  • 13. Cover your bug fix with a regression test
slide-4
SLIDE 4

Recall the rules

1. Understand the requirements 2. Make it fail 3. Simplify the test case

  • 4. Read the right error message

5. Check the plug 6. Separate fact from fiction 7. Divide and conquer 8. Match the tool to the bug 9. One change at a time

  • 10. Keep an audit trail
  • 11. Get a fresh view
  • 12. If you didn’

t fix it, it ain’ t fixed

  • 13. Cover your bug fix with a regression test
slide-5
SLIDE 5

Unit testing frameworks

uniform way of expressing tests manage tests through suites automate testing process

slide-6
SLIDE 6

Remember JUnit?

slide-7
SLIDE 7

We'll use CUnit

http:/ /cunit.sourceforge.net http:/ /cunit.sourceforge.net/doc

slide-8
SLIDE 8

http:/ /cunit.sourceforge.net/doc/introduction.html

slide-9
SLIDE 9

http:/ /cunit.sourceforge.net/doc/introduction.html

slide-10
SLIDE 10

a test

a void -> void method test methods must be part of a test suite, which must in turn be registered with registry, before it will be run

slide-11
SLIDE 11

Assertions

(the most common ones)

CU_ASSERT_TRUE(x) CU_ASSERT_EQUAL(x,y) CU_ASSERT_PTR_EQUAL(x,y) CU_ASSERT_PTR_NULL(x,y) CU_ASSERT_STRING_EQUAL(x,y) CU_ASSERT_DOUBLE_EQUAL(x,y,𝜁) CU_PASS(message) CU_ASSERT_FALSE(x) CU_ASSERT_NOT_EQUAL(x,y) CU_ASSERT_PTR_NOT_EQUAL(x,y) CU_ASSERT_PTR_NOT_NULL(x,y) CU_ASSERT_STRING_NOT_EQUAL(x,y) CU_ASSERT_DOUBLE_NOT_EQUAL(x,y,𝜁) CU_FAIL(message) http:/ /cunit.sourceforge.net/doc/headers/CUnit.h

slide-12
SLIDE 12

LIVE EXAMPLE

slide-13
SLIDE 13

Live coding reconstruction

Production code Test code

Test code is separate from production code, but calls production code to verify its functionality.

slide-14
SLIDE 14

Live coding reconstruction

void test00(void) { int x = 5; int y = -3; int expected = 2; int actual = eval(x, y); CU_ASSERT_EQUAL( expected , actual ); }

A test is a void to void function. Set up inputs and an expected (correct) answer. Compute an actual answer using production code. Compare actual and expected values.

slide-15
SLIDE 15

Live coding reconstruction

void test01(void) { runTest(1,1,2); } void test02(void) { runTest(2,1,3); } void test03(void) { runTest(0,2,2); } void test04(void) { runTest(2,0,2); } /* Runs a test with inputs that *should* pass * and produce an expected result. */ void runTest(int x, int y, int expected) { int actual = eval(x, y); CU_ASSERT_EQUAL( expected , actual ); }

Can simplify writing many tests by using a helper function, runTest.

slide-16
SLIDE 16

Live coding reconstruction

Needed #includes: #include "CUnit.h" #include "Basic.h"

slide-17
SLIDE 17

Live coding reconstruction

/* The main() function for setting up and running the tests. */ int main() { CU_pSuite SuiteValid = NULL; /* initialize the CUnit test registry */ if (CUE_SUCCESS != CU_initialize_registry()) { return CU_get_error(); } /* add a suite to the registry */ SuiteValid = CU_add_suite("Suite_of_tests_with_valid_inputs", NULL, NULL); if (NULL == SuiteValid) { CU_cleanup_registry(); return CU_get_error(); } /* add the tests to SuiteValid */ if ( (NULL == CU_add_test(SuiteValid, "5+(-3)=2", test00)) || (NULL == CU_add_test(SuiteValid, "1+1=2", test01)) ) { CU_cleanup_registry(); return CU_get_error(); } /* Run all tests using the CUnit Basic interface */ CU_basic_set_mode(CU_BRM_VERBOSE); CU_basic_run_tests(); CU_cleanup_registry(); return CU_get_error(); }

slide-18
SLIDE 18

Live coding reconstruction

/* The main() function for setting up and running the tests. */ int main() { CU_pSuite SuiteValid = NULL; /* initialize the CUnit test registry */ if (CUE_SUCCESS != CU_initialize_registry()) { return CU_get_error(); } /* add a suite to the registry */ SuiteValid = CU_add_suite("Suite_of_tests_with_valid_inputs", NULL, NULL); if (NULL == SuiteValid) { CU_cleanup_registry(); return CU_get_error(); } /* add the tests to SuiteValid */ if ( (NULL == CU_add_test(SuiteValid, "5+(-3)=2", test00)) || (NULL == CU_add_test(SuiteValid, "1+1=2", test01)) ) { CU_cleanup_registry(); return CU_get_error(); } /* Run all tests using the CUnit Basic interface */ CU_basic_set_mode(CU_BRM_VERBOSE); CU_basic_run_tests(); CU_cleanup_registry(); return CU_get_error(); }

Create a test suite. In this case the suite is named SuiteValid.

slide-19
SLIDE 19

Live coding reconstruction

/* The main() function for setting up and running the tests. */ int main() { CU_pSuite SuiteValid = NULL; /* initialize the CUnit test registry */ if (CUE_SUCCESS != CU_initialize_registry()) { return CU_get_error(); } /* add a suite to the registry */ SuiteValid = CU_add_suite("Suite_of_tests_with_valid_inputs", NULL, NULL); if (NULL == SuiteValid) { CU_cleanup_registry(); return CU_get_error(); } /* add the tests to SuiteValid */ if ( (NULL == CU_add_test(SuiteValid, "5+(-3)=2", test00)) || (NULL == CU_add_test(SuiteValid, "1+1=2", test01)) ) { CU_cleanup_registry(); return CU_get_error(); } /* Run all tests using the CUnit Basic interface */ CU_basic_set_mode(CU_BRM_VERBOSE); CU_basic_run_tests(); CU_cleanup_registry(); return CU_get_error(); }

Register each test function with the SuiteValid test suite here. If you add more test functions for this suite, add code here to register each test function.

slide-20
SLIDE 20

Live coding reconstruction

/* The main() function for setting up and running the tests. */ int main() { CU_pSuite SuiteValid = NULL; /* initialize the CUnit test registry */ if (CUE_SUCCESS != CU_initialize_registry()) { return CU_get_error(); } /* add a suite to the registry */ SuiteValid = CU_add_suite("Suite_of_tests_with_valid_inputs", NULL, NULL); if (NULL == SuiteValid) { CU_cleanup_registry(); return CU_get_error(); } /* add the tests to SuiteValid */ if ( (NULL == CU_add_test(SuiteValid, "5+(-3)=2", test00)) || (NULL == CU_add_test(SuiteValid, "1+1=2", test01)) || (NULL == CU_add_test(SuiteValid, "1+2=3", test02)) || (NULL == CU_add_test(SuiteValid, "0+2=2", test03)) || (NULL == CU_add_test(SuiteValid, "2+0=2", test04)) ) { CU_cleanup_registry(); return CU_get_error(); } /* Run all tests using the CUnit Basic interface */ CU_basic_set_mode(CU_BRM_VERBOSE); }

This is what it looks like with more test functions registered.

slide-21
SLIDE 21

Branching and merging in git

A sequence of commits all in the master branch.

commit 1 commit 2 commit 3

master

HEAD

slide-22
SLIDE 22

Branching and merging in git

Create a new branch: git branch bugfix

commit 1 commit 2 commit 3

master

HEAD

bugfix

slide-23
SLIDE 23

Branching and merging in git

Move HEAD to new branch git checkout bugfix

commit 1 commit 2 commit 3

master

HEAD

bugfix

slide-24
SLIDE 24

Branching and merging in git

Make a commit on bugfix branch

commit 1 commit 2 commit 3

master

HEAD

bugfix

commit 4

slide-25
SLIDE 25

Branching and merging in git

Make another commit on bugfix branch

commit 1 commit 2 commit 3

master

HEAD

bugfix

commit 4 commit 5

slide-26
SLIDE 26

Branching and merging in git

Check out master again

commit 1 commit 2 commit 3

master

HEAD

bugfix

commit 4 commit 5

slide-27
SLIDE 27

Branching and merging in git

Merge bugfix into

  • master. Since no other

commits were made to master in between this merge is straightforward.

commit 1 commit 2 commit 3

master

HEAD

bugfix

commit 4 commit 5