Microsoft Testing Tour - Functional and Automated Testing
0 likes1,412 views
The document outlines automated and manual testing processes using tools like TFS and Visual Studio, emphasizing the importance of robust UI testing to reduce maintenance overhead and cycle times. It discusses various testing methodologies, including ad-hoc testing, unit testing, and performance testing, while advocating for integrating testing with development to enhance visibility and efficiency. Additionally, it provides best practices for creating and managing automated UI tests and mentions integration with other testing solutions.
![Test -> Windows -> Test View ->
Properties
Select CSV, XML, or SQL
this.UIMap.SimpleTestParams.UIMyTextbox
EditText =
TestContext.DataRow[“col_name"].ToStrin
g();
Databinding to test parameters happens
automatically when converting from
manual test cases](https://image.slidesharecdn.com/testingtour-functionalandautomatedtesting-131119152653-phpapp02/85/Microsoft-Testing-Tour-Functional-and-Automated-Testing-21-320.jpg)
Microsoft Testing Tour - Functional and Automated Testing
- 1. With TFS and Visual Studio Angela Dugan ALM Practice Manager Polaris Solutions
- 2. Angela Dugan
- 3. Manual testing User testing Ad-hoc exploratory testing Planned manual testing Testing toolbox Role tailored tools User Interface Services Business Processes Business Rules and Logic Service integrations Data access Identity Data Automated testing Keyword testing UI automation testing Performance testing Automated testing Unit testing Integration testing Performance testing Load testing Continuous integrations Build | Deploy | Test Lab management automation Dev SIT UAT Stress Prod
- 6. Record and automate UI tests UI regression test needs grow over time Manual UI testing impacts the delivery cycle times Automated UI tests are brittle, time-consuming to maintain Robustly instrument UI tests to reduce maintenance overhead Associate UI tests with a scheduled build Test more functionality in less time Reduce or eliminate repetitive manual testing Reduce cycle time when delivering new features
- 8. Convert the test case to code for enhanced flexibility Generate your Coded UI test from an existing recording, or record a new test case on the fly
- 9. Cross-browser testing support allows automated testing on multiple browsers CodedUI tests interact directly with your app’s UI Tests can be run and monitored on the local machine, or further automated on a virtual machine
- 12. Coded UI tests are part of source control for maximum visibility Coded UI tests run as part of your unit testing suite, enabling developers to detect defects early Even if the look & feel changes, the automated test still executes properly
- 13. Push Squish tests into TFS Import and run Squish GUI tests directly in Visual Studio and view results Preferred partner solution : FrogLogic Associate Squish tests with MTM Test Cases
- 14. Keyword-driven authoring platform using familiar tools Preferred partner solution : LogiGear Library of preprogrammed reusable actions Fully integrated, multi-platform testing
- 15. • • •
- 16. Incident management tools and workflows to integrate operations and development teams in reducing MTTR Reduction of MTTR • SCOM and TFS integrated workflows to manage incidents from occurrence to resolution • One click “Assign to Engineering” from SCOM • Collection of actionable diagnostics in production for development troubleshooting (IntelliTrace)
- 17. Testing the User Interface with Automated UI Tests: http://msdn.microsoft.com/enus/library/dd286726%28v=vs.100%29.aspx CodedUI Testing Walkthroughs: http://msdn.microsoft.com/enus/library/dd286726.aspx CodedUI Best Practices: http://msdn.microsoft.com/enus/library/dd380782.aspx System Testing with Visual Studio: http://msdn.microsoft.com/enus/library/jj620889.aspx
- 19. Mark each step as pass/fail when recording manual tests Carefully consider which test cases make sense for automation, and when Use the Automation Status field of test cases to identify candidates for automation
- 20. Use the Coded UI Test Builder whenever possible Do not modify UIMap.designer.cs as it may be overwritten Create your test as a sequence of methods Create a new test method for each new page, form, or dialog When you create a method, use a meaningful name Try to limit each method to fewer than 10 actions Create each assertion using the Coded UI Test Builder If the UI changes, re-record the test or assertion methods
- 21. Test -> Windows -> Test View -> Properties Select CSV, XML, or SQL this.UIMap.SimpleTestParams.UIMyTextbox EditText = TestContext.DataRow[“col_name"].ToStrin g(); Databinding to test parameters happens automatically when converting from manual test cases
- 22. Searching used to look for all possible controls Filtering used to narrow that list exactly one match X, Y only used to guide where the clicks happen within a control Mouse.Click(uIGOButton, new Point(19, 18));