Test driven development Example

Size: px

Start display at page:

Download "Test driven development Example"

Melvin Farmer
5 years ago
Views:

(H:/ENCM511 or ENCM515) Select FILE NEW CrossProject Use Project name MovingAverage Add src

1 Test driven development Example Developing a moving average filter that can be tested using the EUNIT plug in REVIEW Using the E UNIT testing Framework Activate CCES and select your workspace (H:/ENCM511 or ENCM515) Select FILE NEW CrossProject Use Project name MovingAverage Add src directory to project Add MovingAverage_main.cpp to src directory Add MovingAverage_main.h header to src directory

Using the E UNIT testing Framework Select

2 Using the E UNIT testing Framework Select FILE NEW CrossProject Use Project name MovingAverageTests Set CCES scope to MovingAverageTests project (click on project) Activate E Unit Helper Change Project to E UNIT Project Provide test file and test name Complete project structure build by EUNIT plug in Change your names to these for consistency

two new lines before TEST_FILE_RUN_NOTIFACTION Place cursor at line 22 (Scope into Test File) Click on project name

3 Open the Basic_Test.cpp file build by EUNIT plug in Right click here and select Show line numbers Place cursor at start of line 22 and add two new lines before TEST_FILE_RUN_NOTIFACTION Place cursor at line 22 (Scope into Test File) Click on project name (scope into project) Select E UNIT Helper Add new test to current test file Call the test MovingAverageASM Click OK when asked to reload file KNOW THE STANDARD FORMAT FOR TESTS FOR THE QUIZZES AND EXAM ACTUALLY ON REFERENCE SHEET

Provide the customer requirements (case study) that

of the code This CCES icon shows that CCES does not

to Code Switch to project MovingAverage Note:.

4 Provide the customer requirements (case study) that we need to satisfy Write a Test for the C++ version of the code This CCES icon shows that CCES does not how to use Moving Average Now we switch from Tests to Code Switch to project MovingAverage Note:.h file has a new name Change in the way I thought I needed to use CCES Open MovingAverage.h and add all the necessary prototypes to make the file look like this

Tell the Test Project about the code prototypes Switch to Test project, add the header file info (Error) Change the TEST project INCLUDE path to include the

H:/ENCM5XX/MovingAverage and say OK The CCES what is this icon now disappears from #include line Before Build on Test File GHOST EDITOR error messages As we

5 Tell the Test Project about the code prototypes Switch to Test project, add the header file info (Error) Change the TEST project INCLUDE path to include the MovingAverage project Done under Settings Set scope to MovingAverageTests project (click on it) Use E Unit Helper Add Include Path to Project Search for H:/ENCM5XX/MovingAverage and say OK The CCES what is this icon now disappears from #include line Before Build on Test File GHOST EDITOR error messages As we will see this is a ghost error. CCES does not yet know it knows about MovingAverageCPP This error should disappear after we compile Seems to be fixed in 2.0.0

After Build Error has disappeared Also CCES indicates that it knows New error identified DOUBLE

Helper either is over helpful or I have changed names too often Investigate more details later

h Before we rebuild what should we expect No syntax errors in Test code Linker MUST complain it

6 After Build Error has disappeared Also CCES indicates that it knows New error identified DOUBLE CLICK on red lighted message line then CCES editor will jump to error file and error line E Unit Helper either is over helpful or I have changed names too often Investigate more details later For now comment out the line // #include Basic_MovingAverage.h Before we rebuild what should we expect No syntax errors in Test code Linker MUST complain it can t find the code MovingAverageCPP (since we have not built it) Linker will not complain about MovingAverageASM (since we did not use it)

Test Driven Development Write a Stub Test should fail Add MovingAverageCPP.

check syntax Refactoring Stage 1 The project MovingAverage is misnamed This will

many times in many projects Meaning we want a library Rename project as

7 Test Driven Development Write a Stub Test should fail Add MovingAverageCPP.cpp file to MovingAverage project Right click on file Use build selected file to check syntax Refactoring Stage 1 The project MovingAverage is misnamed This will end up being a collection of digital signal processing functions that will be used many times in many projects Meaning we want a library Rename project as MovingAverageLibrary Libraries don t have main( ) routine so delete the main in MovingAverage_main.cpp

Right click on MovingAverageLibrary project name and select Properties C / C++ Build Settings

dlb file) Click OK (error message click through WAIL) Right click on MovingAverageLibrary Click

Set scope to MovingAverageTests Use E Unit Helper Add library to add to MovingAverageTests

switching baaaaaack from C++ code and optimized C++ code If you Optimize the library then the

8 Right click on MovingAverageLibrary project name and select Properties C / C++ Build Settings Build Artifact Change from Executable (.dxe file) to Static Library (.dlb file) Click OK (error message click through WAIL) Right click on MovingAverageLibrary Click on Build Project Refactoring Now we need to tell the tests that the library is available for use Set scope to MovingAverageTests Use E Unit Helper Add library to add to MovingAverageTests project Can be found in MovingAverageLibrary / debug Build Test project NOTE: You will be switching baaaaaack from C++ code and optimized C++ code If you Optimize the library then the library moves from Debug directory to Release directory. MY PREFERENCE Optimize just the file then the library is always in Debug directory

Not enough memory error (Does this occur with SHARC?

(Use release or optimized mode WAIL) Fix 2 Use both internal and

change the LDF Loader Descriptor File (Necessary for SHARC?

9 Not enough memory error (Does this occur with SHARC?) Blackfin on chip program memory is small Fix 1 make library smaller (Use release or optimized mode WAIL) Fix 2 Use both internal and external memory Doing Fix 2 by Right click on MovingAverageTests / system.svc and select Open with System Configuration Editor We need to set change the LDF Loader Descriptor File (Necessary for SHARC?) Click here and change the LDF settings to allow system to use external memory Control S to save Then rebuild project Download to the processor, run, and THE TEST MUST FAIL. TEST of the TEST

10 Check Disassembly Window for Completion Check Console Window for Results NOT THE ANSWER WE EXPECTED Nothing about MovingAverageCPP( ) is failing!!!! Forgot to add the test code Fix but hidden project defect revealed

Select MovingAverageTests as project to clean This removes all files built and does something called update project dependencies (Who does what to whom) Rebuilds the project,

11 Remember we changed the MovingAverageLibaray project name! Fix by using EUNIT Helper to add MovingAverageLibrary to the include path This fails as CCES is confused about what include path to use Select menu item Project Clean Project Select MovingAverageTests as project to clean This removes all files built and does something called update project dependencies (Who does what to whom) Rebuilds the project, reloads the project and runs it Quick check What happens if we change MovingAverageCPP.cpp Change MovingAverageCPP.cpp to return 42 Rebuild MovingAverageLibrary Project Rebuild and Run MovingAverageTests Project DOES NOT REBUILD until CLEAN MovingAverageTests Find a way to make this dependency automatic

12 Found this dependency option Reported to Engineering Zone does not work Seems to be a known Eclipse problem that CCES has inherited. Note to self Clicking here does nothing Really annoying See if fixed in or Now we build the simplest function to make the Test pass

13 Why does the code fail? What other tests should we use? How many Tests? Make sure your tests are valid DEFECTIVE TEST

14 Can t see the failures for the successes? RunAllTests(true, true /* expected fails */, false /* successes */); Final refactored format for ENCM5XX directory

Building a COFFEE POT simulation on CCESS for Blackfin BF533

Building a COFFEE POT simulation on CCESS 2.6.0 for Blackfin BF533 Last lecture covered some detailed ideas Let step back and do something simpler to get an introduction of ideas needed for Lab0 and Assignment