OpenSAP Wtc1 Week 2 All Slides

Week 2: Test-Driven Development
Unit 1: Introduction to Test-Driven Development

Introduction to Test-Driven Development
Process of test-driven development (TDD)
1. Write no product code except to pass Refactor

a failing (red) test or a syntax error Code
2. Write only enough of a test to

demonstrate a failure (next small step) Tests
All tests
3. Write only enough product code to pass
pass the test
Test not
complete;
After all tests pass (are green) again, Write
repeat
clean up the test by refactoring! Small product
Requirements code
Test fails
Write test code

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2
Introduction to Test-Driven Development
Benefits of test-driven development
▪ Test development drives feature development

▪ Focus on the essentials
 Tests codify only the requirements
 Only necessary product code is written
▪ The tests were seen red once and then switched
to green by adjusting product code, which proves
the test actually covers a new case
▪ Product code is testable by design
▪ Bugs were introduced just now and can be fixed
right away
▪ Product code starts with the simplest code
needed right now

Thank you.
Contact information:
open@sap.com
© 2017 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components
of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated
companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are
set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release
any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products,
and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The
information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various
risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements,
and they should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company)
in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.
See http://global.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Unit 2: Demo of TDD on Money Machine
Demo of TDD on Money Machine
Extend the money machine API – Demo
Provide a function
get_amount_in_notes( )
which calculates the amount returned in notes.
The development should be done according to

the test-driven development process.

Thank you.
open@sap.com
Unit 3: Exercise – TDD: Money Machine
Exercise – TDD: Money Machine
Extend the money machine API – Exercise
Provide a function Euro Coins: 1, 2
get_change( ) Euro Notes: 5,10,20,50,100,200,500
which returns the highest possible Euro notes Input type shall be an integer
and Euro coins for a given amount.
Return type shall be tt_change:
TYPES: BEGIN OF ty_change,
amount TYPE i,
type TYPE string,
The development should be done according to END OF ty_change.
the test-driven development process. TYPES tt_change TYPE STANDARD TABLE OF ty_change
WITH DEFAULT KEY.
Possible test input values

Use Class: ZCL_WTC_MONEY_MACHINE 1,2,3,4,5,8,10,15,20,50,85,100,200,500,688
0,-11

Thank you.
open@sap.com
Unit 4: Review of Sample Solution
Review of Sample Solution
TDD: Money Machine

Thank you.
open@sap.com

OpenSAP Wtc1 Week 2 All Slides

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenSAP Wtc1 Week 2 All Slides

Uploaded by

Copyright:

Available Formats

Week 2: Test-Driven Development

Unit 1: Introduction to Test-Driven Development

1. Write no product code except to pass Refactor

2. Write only enough of a test to

Write test code

▪ Test development drives feature development

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

which calculates the amount returned in notes.

The development should be done according to

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Provide a function Euro Coins: 1, 2

get_change( ) Euro Notes: 5,10,20,50,100,200,500

Possible test input values

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

You might also like