Testing with Visual Studio 2012 Agile TMap

1. Module 06
Feedback and
Operations

2. Topics

3. Continuous Feedback
Agile techniques are effective, because they embrace continuous feedback.
Continuous feedback helps minimize the snowball effect of a fault.

4. Feedback loops are part of
every phase of the lifecycle.
Feedback can be internal (team)
or external (stakeholders).
Feedback Loops

5. Storyboarding and Prototyping
Supporting
the team
Validates
Business Needs
Prototypes
Simulations
Clarifies Intent
Done at the
beginning of a sprint

6. Create custom shapes to
re-use throughout your
application.
Create realistic mock-ups of your UI for
early approval, and attach them to work
items so developers know what to build
Hundreds of pre-built shapes,
from iOS to Windows Phone
to navigation animations

7. Code Reviews
Supporting
the team
Validates
Business Needs
Code Review
Code Analysis
Done ad-hoc
during a sprint

8. Continuous User Feedback
Validates
Business Needs
Supporting the
Product
Alpha/Beta Tests
Sprint Review
At the End of a sprint
or when PBI is finished.

9. Free Feedback client app
guides stakeholders through
the feedback process
Provide rich feedback, including
audio/video recordings,
screenshots and additional files

10. Automatically send
feedback requests to
stakeholders via email
Elicit actionable feedback by
focusing feedback on specific
areas of your application

11. Free client utility guides
stakeholders through the
feedback process
Enable detailed, rich text
feedback and a star rating system
Capture voice, video, screenshots,
attach files, or any combination

12. Stakeholder feedback is
captured as a work item in TFS
Create new work items based on
stakeholder feedback

13. Demo
Feedback Management
PowerPoint Storyboarding

14. DevOps

15. In Production, nobody hears you scream!

16. Development vs. Operations

17. Integrated Incident Management
Operations
Development and
Testing

18. Production incident alert
in operations system
Assign code related incidents to development
Development system incident
reference in operations tool
Incident in development system

19. Request additional diagnostics from operations
Request for additional diagnostics in operations system

20. Generate IntelliTrace logs from within SCOM
IntelliTrace logs
collected by operations
in development system
Actionable debugging
using IntelliTrace logs

21. IntelliTrace in Production
Preemptive Analytics
Gathering Actionable Data in Production
Monitor

22. With production errors, root causes are difficult to
identify, debug and resolve
IntelliTrace in Production is easy to run, and collects critical IntelliTrace logs with minimal impact to server performance.
Developers, who are already familiar with using this data in test environments, now have the data to speed root cause
analysis of production bugs, and rapidly identify the needed code fix.
Actionable diagnostics
IntelliTrace in Production speeds up debugging and shortens code fix times.
IntelliTrace in Production

23. Instrumentation in minutes with Dotfuscator injection
Extensible rules detect and prioritize production
incidents reflecting organizational priorities
Work Items are created and updated in near real-time
ensuring efficient, feedback driven response across
.NET, JavaScript, C++, Java and mobile surfaces

24. Monitor applications across enterprise domains and
onto external networks and consumer devices.
Enforce opt-in policy, manage dropped networks
and secure data on the wire.
Collect custom data and monitor unhandled,
caught and thrown exceptions.

25. Work Items are automatically created or updated when patterns are
detected in production.
Rules are easily mapped to instrumented applications
and can be reused, extended and developed to capture
business priorities and integrate with other systems
including CRM, ERP and other mission-critical platforms.

26. Demo
IntelliTrace
PreEmptive Analytics

27. To learn from experiencegained during this test and to preservetestware for reuse in a future test. The point here is
that with changes and associated maintenance tests, the testware only requires adjustment, so that it is not necessary
to design a completely new test. During the test process, efforts are made to keep the test cases corresponding with
the test basis and the developedsystem. If necessary, the selected test cases should be updated.
http://www.tmap.net/en/tmap/4-essentials/structured-test-process/acceptance-and-system/completion-phase
The Completion Phase