- Posted by justin on September 11, 2005
Summary: I attended the Team System Pre-conference session today. The first part of the session was a marketing overview kind of session. There was a lot of good information. Based off the marketing material, it looks like something that I need to look into to see if it would improve the process on my projects or if it is going to just add overhead for the sake for better tracking. The 2nd half of the session was nothing but demos. The first thing that I noticed with the demo is that the integration between project or excel is still not fully automated like it needs to be so there is some overhead from a PM standpoint. Concept of VSTS is very good but I think it is not completely ready for prime time. Maybe this will change by the time the final release comes up.
Notes from Session:
- July CTP of VSTS using June Version of SQL2k5 so you need 2 machines to run the beta. One for VSTS and one for Sql2k5
- Everything can be extended. Config is based on XML. Easily can extend.
- Sql2k5 Express includes reporting services. Much easier to deploy than msde
- Everything is built on top of web services.
- Project and Excel plug-ins
- Few Editions:
- Team System:
- Team Edition for Software Architects
- Team Edition for Software Developers
- Team Edition for Software Testers
- Team Foundation Server
- Sits in the backend, accessed by http or over network
- provides us with checking in and out code
- reporting services
- process tracking
- Team Suite
- Includes all 3 of the team system editions
- Features by Edition
- Class Designer
- Part of VS Pro Edition
- UI for designing classes.
- It is a visualization of the code
- 2 representation: 1.) text 2.) graphical
- Architects
- App Designer: How the app work logically
- Logical Infra Designer: How the app is deployed
- Deployment Designer: What is required to deployed
- service packs
- os
- components
- etc
- Visio and Uml modeling
- Team Foundation Client
- VS Pro Edition
- Collectively called whitehorse
- Developers
- Dynamic Code Analyzer:
- Static Code Analyzer:
- Code Profiler: Unit Testing:
- Code Coverage
- Team Foundation Client
- VS Pro Edition
- Testers
- Load Testings
- Manual Testing
- Test case management
- Unit Testings
- Code Coverage
- Team Foundation Client
- VS Pro Edition
-
Team Foundation Services
-
There is not web UI to log work items. Have to use VS to log them
-
Team Foundation Version Control
-
Description: Integrated Software Lifecycle suite
-
Team Size: scalable
-
Storage: sql2k5
-
Security: windows integrated
-
Remote Access: optimized web service
-
Multiple Checkout: yes, thanks to the merge engine
-
VSS 2005
-
Team system Extensibility
-
Team System Sensibility tool kit. free download. will eventually be part of the SDK
-
Team Foundation Services
-
Add your own methodology templates
-
VSIP have already announced extensions:
-
Borland
-
Amerpoint
-
Olenick and Associates
-
Brightwork
-
Osellus
-
Team Foundation Beta will contain a Go Live License when VS2005 is released Nov 7th.
-
Team Foundation Server will be released Q1 06. VS2005 released Nov 7th. Team Foundation Beta 3 will be released Nov 7th
-
Team System for Project Managers
-
Team Explorer
-
where in vs2005 where you can view work items, bugs. can add work items/bugs
-
can launch reports
-
everything add thru vs is immediately available thru the sharepoint portal
-
Team System for Architects
-
Developing for Operations
-
two cools SDKS out that you can play with
-
SDM:
-
Logical Datacenter diagrams
-
app diagrams
-
SOA designer
-
various services that are running and are interacting with other services
-
how the application connects to other applications/services.
-
can generate the projects based off the diagram.
-
builds all of the web service proxies
-
currently they do not implement wse
-
tell it how security works
-
can reverse engineer current projects
-
Team System for Developers
-
Unit Testing
-
More powerful and easier to use than NUnit
-
Code coverage does not ensure quality. It just means that you are at least testing something. If you have a lot of untested code with business logic then you should be writing a lot more automated unit tests.
-
Rolls up report into nice output that you can easily/quickly tell how much you are covered.
-
When doing a build can have it run code coverage as part of the build
-
Can define checkin policies
-
Static Analysis
-
basically FxCop
-
Easier to write own rules
-
Tests your code for common problems, best practices, naming guidelines, etc.
-
A ton of built in items to check for.
-
if code fails, then it can reject the code and flag that it needs to be fixed before a release can be done
-
Integrated Checkin
- Team System for Testers
- Problem Space
- Testing tools are not integrated
- No version control for tests
- No integrated notification mechanism
- Activities
- Unit testing and code coverage (overlap with dev)
- Web testing (record and playback URL interactions)
- Load testing (simulate multiple users)
- Test management (manual and 3rd party tests)
- 3rd party testing software is being integrated in such as mercury
- Generic Test
- Command line test. Can be used to call external test that returns results and capture them and store the results in VSTS
- Web Testing
- Have access to viewstate
- Can simulate users and think times
- think times: basically add a buffer in for the time a user takes to do something, example: user pulls up page, reads some help, then fills out form. If this took 30 seconds, you can tell the test to 30 for seconds before going on.
- Testing Web Applications is important
- What is response time for common tasks
- has the upgrade broken basic functionality
- do searches still work
- many external, third-party solutions
- variations in capability and flexibility
- not integrated
- web testing in team system
- any URL that is http based
- recorded or code based;with validation
- Load Testing
- Is there a tool integrated for windows forms testing? Microsoft does not provide one but some third party vendors are working on them.
- Manual Test
- Questionnaire. Basically a problem resolution document
- Can be used for stuff that can not be automated.
- Can do distributed load testing
- Control from one machine but use multiple machines to do the testing.
- Can define how much of the load each machine takes and how many threads each machine starts
- How does you app work under load
- which operations see the most impact?
- what is the processor and disk utilization
- Load test an existing unit test
- Load test an existing web test
- Many ways to visualize the results
- Team System for Everyone Else
- Can access real-time reports on the portal. Can be customized for each user.
- Can use excel or project to maintain work items
- Can use team Explorer or command-line utilities to view/edit projects artifacts – no need for VS
- Built on Sharepoint Web Services. Can integrate into your own web site.
- Does not require Sharepoint portal server.
- Is optimized for Sharepoint WSS.
- Summary:
- VS 2005 Team System is for the entire team, not just the developers
- All the tools are integrated into VS
- Not all team members need VS
- Excel, Project, Team Explorer, and IE
- Attendee Questions:
- for load testing with cpu performance it does not require manual analysis but it will be added directly.
- if you need testing but also need architect, you will want to install Team Suite. You can also install multiple editions of Team System onto the same system. The CTP are Team Suite.
- Resources:
- web sites:
- Blogs
- Books
- Visual Studio Team System. Should be available in October.
- Demo:
- Part 1: Project Managers and Architects
- Create and configure a new team project
- Assign work items
- create and validate architectural diagrams
- Part 2: Developers, Tests, Deployment
- Implement the application, using class designer
- Check-in, check-out, shelve, and merge code
- Run unit tests, code coverage, and static analysis tests
- run web tests and load tests
- generate and analyze reports, including a deployment report
- Scenario
- AdventureWorks wants to create a new web app
- Enterprise blog application n-tier
- team will be 1pm, 1 ia, 1 sa, 1 dev, 1 tester
- must use sql2k5
- must use web services
- must be 3 tier
- must be able to deploy to new datacenter
- all code must be unit tested
- all code must follow defined “best practices”
- all code must be checked into/out of SCC
- development team must use vsts
- project has to be shipping in 3 hours
- Team Explorer is available in all versions. It is how people get access to add/modify work items, project documents,etc.
- Each person that is going to change data needs a cal license. All users have read-only access by default and do not require a cal license
- Some Reports:
- Work Remaining: Show Remaining Work, Resolved, and Closed
- Velocity of Bug Fixes
- Unplanned Work: amount of planned work versus unplanned
- Quality Indicators: # of test that passed, failed, ignored, and amount of code coverage
- Code Churn: detects when a project will fail. According to Microsoft they can predicted 93% of the time if the project will fail.
- Bug Rates: Active, Newly, and Resolved bugs.
- Reactivations: How many false task and bug item do we have
- Bugs by priority: Are we finding and triaging the right bugs?
- Actual Quality versus Planning Velocity: How fast can we go compared to how many bugs we generate.
- Can easily build your own reports using the built in reporting services.
- Does not completely integrate with Project and Excel. There is still a decent amount of manual steps that a PM would have to do.
- Reports can be at the project level or drilled all the way down to an individual developer.
- Can associate work items to other work items so that you get a dependency.