testing telephony: it's not all terrible

P A G E

Testing Telephony - It’s not all terrible

Ben Langfeld@[email protected]

Lance Gleason@[email protected]

mailto:[email protected]




P A G E

P A G E

WTF GUYS?!

P A G E

UNIT TESTING ADHEARSION APPLICATIONS

3

P A G E

Adhearsion components can be unit tested like anything else

4

P A G E

If using ActiveRecord or any other ORM, move as much domain logic as possible into your models

5

P A G E

State-full telephony fits into a set of domain models

6

P A G E

Specify the hell out of your models

7

P A G E

When possible, encapsulate dialplan DSL methods and/or any other code which touches the voice platform for ease of

mocking

8

P A G E

INTEGRATION TESTING

9

P A G E

QA TELEPHONY APPLICATIONS IS HARD

10

P A G E

MANY COMPLEX SCENARIOS

11

P A G E

VERY COMPLEX BRANCHING FLOW

12

P A G E

LOTS OF REGRESSIONS

13

P A G E

14

P A G E

AUTOMATED INTEGRATION TESTING

14

P A G E


14

NÜECHO

P A G E


14

$$$NÜECHO

P A G E


14

PROPRIETARY$$$NÜECHO

P A G E


14

TELTONE


P A G E


14

TELTONE


DITTO

P A G E

15

P A G E

CUCUMBER-VOIP

15

P A G E

CUCUMBER-VOIP

15

$0, OPEN SOURCE, EXTENSIBLE

P A G E

16

P A G E

17

P A G E

(TOTALLY FAKED - THERE’S BUGS)

18

P A G E

19

P A G E

TEST THE ENTIRE STACK, INCLUDING THE VOICE INTERACTION AND MEDIA

20

P A G E

GITHUB.COM/BENLANGFELD/CUCUMBER-VOIP

21

P A G E

Quest ions?

Technology