TLA13-HOL - Visual Studio Team System code name "Rosario": Team Development
Unit Test management
Everytime you run tests it automatically creates a new test run with a default name and records all the test results. So you keep a history of what tests were run and when and which ones passed or failed.
Types of tests you can create
VS is used to managed both
unit-tests and
integration tests. You can create:
- coded UI tests (where you write UI tests using automation as opposed to record/replay)
- Database unit-tests to test T-SQL stored procedures.
- Generic tests. This is actually an external program that will look like an ordinary test from within visual studio. You specify the command line arguments to call the external program. You have the option to redirect the standard output / error to the test results or not.
- Load tests. That's quite fun: you can simulate heavy load conditions with many users. Among other things you can define a load pattern (constant load or increasing load) and the distribution (percentage of appareance for each test).
- Manual tests: simple text file describing a manual test procedure. This is there for auditing purposes only obviously.
- Ordered test: specify a list of tests to be run in a specific sequence in the situation where order counts (that's for integration tests only, unit-tests should not be order dependent)
Impact analysis: as you change code, VS gives you the list of recommended tests (tests that should be re-run as a result of your changes)
No comments:
Post a Comment