@ClemensReijnen

Recent posts

Tags

Categories

Navigation

Pages

Archive

Blogroll

    Disclaimer

    The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

    Channel 9 video series: UML with VS2010

    http://blogs.msdn.com/b/vsarch/archive/2010/07/29/channel-9-screencast-series-uml-with-vs2010.aspx

    very nice series of video’s explaining usages scenario’s for UML within VS2010

    image


  • Part 1: Brainstorming a Project
  • Part 2: Organizing Features Into Use Cases
  • Part 3: Modeling the Business Domain
  • Part 4: Capturing Business Workflows
  • Part 5: Architecting an Application
  • Part 6: Designing a Project's Physical Structure
  • Part 7: Sketching Interactions with Sequence Diagrams
  • Part 8: Revealing Responsibilities with Class Diagrams
  • Part 9: Organizing and Managing Your Models
  • Presentation: TMap for VS2010, Testing Practices with ALM tools

    My deck and demo’s for TMap® meets Visual Studio®, München.

    One funny thing I didn’t know, in Germany they knock on the table instead off clapping...

    Untitled

    the Deck [from SlideShare]

     

    The 5 demo’s [from YouTube]

    Demo 1 for TMap for VS2010 (Munchen) presentation, Upload TMap Process Template and create a new project.
    Demo 2 for TMap for VS2010 (Munchen) presentation, Edit the TMap Process Template with TFS powertool Process Editor.
    Demo 3 for TMap for VS2010 (Munchen) presentation,Test Case Writing with a focus on shared steps, validations and parameters
    Demo 4 for TMap for VS2010 (Munchen) presentation, Run the in demo 3 created test cases. focus on shared step, validations and parameters
    Demo 5 for TMap for VS2010 (Munchen) presentation, Create a codedUI test from the in demo 3 created test cases. Focus on shared step, parameters and validation/ assertion
     

    and two pictures.

    22072010095 22072010102
    My German colleagues explaining TMap… Had the most scary flight home ever… it was a rollercoaster.
    Posted: Jul 25 2010, 03:12 by ClemensReijnen | Comments (0) RSS comment feed |
    Filed under: ALM | VS2010 | TMap

    Microsoft Test Manager Test Artifact organization…

    It is still a bit complicated, or better a bit confusing, how the different parts within Microsoft Test Manager are organized. This post is a try to clear things a bit [mostly for myself Smile]… please respond if I made a mistake!

    On MSDN this image is shown to explain the organization of test artifacts, but this is a simplification, the reality is a bit more sophisticated and complex. For example test cases can exist in different suites, plans and even different team projects.   

    Components of a Test Plan

     

    A different view…

    And again, correct me if I’m wrong…
    See image below; a project collection has multiple team projects and a team project only can live in one project collection. A test plan only exists in one team project, while team projects have multiple test plans and a test case belongs to a single team project, where team projects can have more test cases.

    testartifactorg

    So far no problem… With test cases and test plans it gets confusing. When you read the diagram, a test case can live in different test plans from different team projects [within the project collection]. The proof is in the image below ”a test plan with test cases from multiple team projects”… you can accomplish this by adding excising test cases, just change the query.

    Picture1

    The only reason why you want to add test cases from other team projects in our current test plan is when you want to check something from another application before you continue testing your project, maybe the availability of a service where you depend on.

    Anyway, it can get a bit confusing… the other thing what you need to keep in mind, it isn’t a ‘deep’ copy of the test case when you copy-past test cases to other test plans, it is a link-copy, the ID stays the same..! 

    2

    The relation and composition of test runs and test results is another dependency which can get confusing, specially when you have test cases linked to many different test plans and team projects. A test plan has test runs, every time you run a test case or a set of test cases a run is added to the test plan. For test cases which are executed in this test run a test result is collected [which information can be collected for bug reports].

    Capture

    So, we can have succeeding test runs with test cases which are failing in other test runs Thinking smile… We definitely need some more reporting to get some better understanding about that, a view in which test run [and test plan/ team project] a test case has run with which result for example.

    I didn’t mention the relationship / linking you can create with other work item types, but I do think you can imaging it even can get more complex. The “Work Item Visualizer for TFS 2010” on Visual Studio Gallery is a great tool for clarifying this.

    Presentation: Work Agile with VS2010

    Architecture Journal Article: Models and Application Life-Cycle Management

    This article discusses the creation and maintenance of consistent, correct, and communicative software architecture by using Microsoft Visual Studio 2010.

    bb410935_JournalLogo(en-us,MSDN_10)


    Setting up, validating, and maintaining consistent, correct, and communicative software architecture in its context and interaction with its environment is no trivial task.

    A new architecture needs to be created. But how do you know if this architecture is good? ff805120_Figure_1(en-us,MSDN_10)Covering all areas, dealing with all the requirements and quality attributes is difficult; but forgetting to discuss one or more is easy and will leave space for assumptions.

    Because of changing requirements, your architecture needs to be changed. But how do you know if it is still consistent? Unstable documents and models will confuse the development and test teams, who will not know what to build or what the intention of the system is.

    How can you make practical use of the Microsoft Visual Studio 2010 modeling capabilities in the application life cycle and an architectural approach, to cover these challenges and create good software architecture?

    Read the article

    SCRUM, SCRUM… SCRUM..!

    Attending this week [a full seven day week] two amazing courses from scrum.org, with the goal to become a scrum developer trainer…

    Professional Scrum Developer
    Team-based training for Agile software developers

    Scrum in Depth
    Advanced class for ScrumMasters

    30062010031

    So, expect some more scum related posts in the future Hot smile

    Visual Studio Architecture Guidance - Use UML Models for Testing

    To promote our ranger work a bit more… I want to high light a specific scenario… create tests from UML models. I already played with this scenario from an automation perspective 2 years ago, when VS2010 was still in CTP. [see the bad quality video, already watched more as 17.000 time Confused smile]

    Generate Testcases

    Anyway, there are two common test design techniques that are used to specify test cases based on UML. The first is the Process cycle test[1] (PCT) which uses UML activity diagrams. The other one is Use Case Test[2] (UCT) which is based on Use Case diagrams.

    Still on my backlog to make a fully working automation for these [waiting for Feature Builder to go RTM]. But, you also can do it manually, as you can see in the hands-on-labs.

    Task 1: Open Activity Diagram

    • 1. Open the TailSpinToys solution in Visual Studio 2010

    • 2. Open CoreShoppingExperience.activitydiagram

    Task 2: Create logical test cases based on PCT

    val

    • · Path combinations for decision point 1: (1,2) and (1,3);

    • · Path combinations for decision point 2: (2,4) and (3,4);

    Based on PCT path combinations for test measure 2 are 1-2-4 and 1-3-4 for these paths test cases should be created.

    … and create these TestCases in Microsoft Test Manager

    val2

    Still a great ALM scenario where the different rolls in the lifecycle use artifacts from each other from that central repository.

    [first time use of the wave 4 live writer, still like it…]