Test Tooling in Visual Studio 2012 an overview.

1. TechNight
Clemens Reijnen

2. Continuous
Quality

3. ‘ility’ testing
Alpha/ Beta
Component Tests
Examples
Exploratory Testing
Functional Testing
Load Testing
Performance
Prototypes
Scenarios
Security Testing
Simulations
Story Tests
Unit Tests
Usability Testing
User Acceptance Testing

6. Every test must be able to rely on previous
tests
All test types are supported by Visual Studio
2012
http://www.tmap.net/en/tmap/4-essentials/structured-test-process/master-test-plan

7. Exploratory Testing
Functional Testing Scenarios
Examples Usability Testing
Story Tests User Acceptance
Prototypes Testing
Simulations Alpha/ Beta
Performance &
Load Testing
Unit Tests Security Testing
Component Tests ‘ility’ testing

8. Exploratory Testing
Functional Testing Scenarios
Examples Usability Testing
Story Tests User Acceptance
Prototypes Testing
Simulations Alpha/ Beta
Performance &
Load Testing
Unit Tests Security Testing
Component Tests ‘ility’ testing

9. Exploratory Testing
Functional Testing Scenarios
Examples Usability Testing
Story Tests User Acceptance
Prototypes Testing
Simulations Alpha/ Beta
Performance &
Load Testing
Unit Tests Security Testing
Component Tests ‘ility’ testing

10. Unit Tests
Component Tests

11. Isolate each part of the program and show that the
individual parts are correct.
Crafted during the sprint, executed continuously.

13. Developer Focused
Testing
Red Green Refactor
Pluggable test
frameworks
Run test after build

14. Run from Unit Test
Explorer

15. Isolating code for better testing
Shims – run-time interception lets you replace call
Stubs – concrete implementations of interfaces or abstract
classes
Strive to refactor the code so you don’t need the Shims anymo

16. Unit Tests
Component Tests

17. Find semantically
similar code

18. Understanding
Class Coupling

19. Check coding
rules

21. Functional Testing
Examples
Story Tests
Prototypes
Simulations

22. Prototypes
Simulations
Beginning of the sprint
make pbi’s clear.

25. Test Runner
Action Recording

28. Test Automation Levels 0 No automation
1 Shared Steps with action
recording
2 Test Cases with action recording
3 Generated Coded UI
4 Customized Coded UI

29. Test Automation Levels
Number of test cases per level in a
sprint.

30. Performance &
Load Testing
Security Testing
‘ility’ testing

31. Performance test:
To determine or validate
speed, scalability, and/or
proof business
stability. needs
Load test:
To verify application
behavior under normal Supporting the
Product
and peak load conditions.

35. Exploratory Testing
Scenarios
Usability Testing
User Acceptance
Testing
Alpha/ Beta

36. Simultaneous
test design and
execution. Supporting the
Product
Test working
software.
support the
implementation

39. http://www.tmap.net/en/tmap/4-essentials/structured-test-process/acceptance-and-system/planning-phase

43. Title / Description
(describing the story)
Acceptance Criteria:
(presented as scenarios)

44. Logical Test Cases
Test Coverage

45. "Are you done yet?“
Shared Understanding

46. Get a Team
Get Testing knowledge
Have Test Tasks

47. Define Test Cases based on the PCT2 Test Design
Technique

49. Every phase has it’s specific test tasks
Planning, Control, Preparing, Specification, Execution, Completion, Control, Infrastructure.

50. The PBI isn’t ready to be tested till coding is done.