Automated bdd style acceptance tests for MS Office add-ins
26
-
Upload
dzmitry-lahoda -
Category
Software
-
view
52 -
download
1
description
Outlined of talk about automated testing MS Office add-ins and WPF applications
Transcript of Automated bdd style acceptance tests for MS Office add-ins
Show Cucumber feature, write test, copy stubs, copy implementation, show old code, paste new
Show test, run test, run report generation, show created documents, show TestStack.White, AutoItX from .NET
●
●
●
●
●
●
●
●
●
●
●
●
●
IThreadingService, IViewService, ViewModel, ICommand, Dependency Injection Container, UnitWrappers
●
●
●
●
●
Show grouped DI container registrations, images, native dll
●
●
●●●●●
●
●
●
●
●
●
●
●
●
●
Feature Unit Integration(TDD-style)
BDD-style acceptance
Run time 0.1s 2-10s 15s
Asserts 1 2 5
What to test ? ? Story and “acceptance” term say what
Class Several classes and external system
End-to-end real world scenario
Understand ability Good Bad Good
Amount of tests 30 5 2
Audience Dev ? Not only Dev
Show sites of MSTestcontrib, StoryQ, SpecFlow, some big unit test with “because” and “when”/”then”, F# and IronPython testing expressiveness
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
●
Tests are code and make production code:Cohesive, DecoupledExtensible, ReusableDocumented, Refactorable
http://msdn.microsoft.com/en-us/library/windows/desktop/dd318452.aspx
There is no technological difference between automation and production code.Developers should be made thinking in terms of users via BDD
●
●
●
