0

Fear, A Major Speed Bump on the Road to Quality

by Angela 3. February 2017 22:26

I warned you that I’d be blogging about the “messiness” of ALM and DevOps consulting. And this is a long one so grab a cup of coffee, tea, or cocktail of your choice (whatever I won’t judge). It’s actually based on something I wrote for the QAI Quest Magazine. If you haven’t checked out the CQAA (Chicago Quality Assurance Association) community or their upcoming QUEST conference in Chicago this April, I highly recommend it!

Anyway, here is the article:

A large part of my job as a scrum master and agile coach is focusing on quality. Quality of process, quality of teams, and quality of software. While all of these can be challenging to improve, one of the hardest to tackle is quality of the team. I’m not talking about individual’s skillsets, although that is important. I’m talking about the ability of the team to work together as a WHOLE. In my experience, teams that cannot accomplish this cannot produce a quality product. Missed requirements, sloppy handoffs, miscommunication of what is “done”, and a host of other issues arise when the team just can’t seem to come together in a truly open and collaborative environment. Causes for this failure are complex and will vary from team to team. But one that I run into time and time again is fear. Yes, fear!

I’m not a psychologist and I don’t purport to know all the answers, but I can speak from experience - both in terms of myself and what I see in others. I have seen fear manifest itself in the following situations:

· Underestimating feature delivery times to hide a lack of confidence, often leading to painful sprint reviews when committed features aren’t delivered on time, or not at all.

· Code being integrated too soon to avoid being late, resulting in bugs “leaking” into production.

· Misunderstood requirements being implemented without question, and promptly being rejected by QA or a frustrated product owner.

· Resentment when team members feel someone is not pulling their weight, when in reality that person is silently struggling.

· Failure by team members to ask for clarification because everyone else surely must “get it”.

The fear of being seen as not good enough or smart enough by our peers is real and pervasive in IT. Ironically, the end result of hiding our struggles is often working extra hours and even cutting corners to make the unrealistic deadlines that we set for ourselves. This inevitably leads to doing the very thing we are fearful of … letting people down.

Tying this back to quality:

· Imagine if the team was afraid to admit that a requirement was vague, that it would be extremely complex to develop, or almost impossible to adequately test.

· Imagine if they assumed they’d figure it out as they go and plowed ahead.

· Imagine if someone on the team rushed to complete a feature and skimped on testing to prevent blowing their estimates because of fear of retribution for being wrong.

You probably don’t have to imagine it. It’s likely happening on your team right now but no one is talking about it! So, what can you do once you’ve realized that fear is holding you or your team back? What I have learned on my own journey is that it’s not enough to recognize when I am acting from a place of fear; I also have to recognize it in others. And much like quality, it is EVERYONE’S responsibility to create a collaborative and supportive environment.

As a Scrum Master, here are some of the things that I ask myself in order to help address fear on my teams.

· Is someone new to the team, or to their role, and clearly feeling overwhelmed or struggling to fit in?

· Is someone is hesitating to speak up when they clearly have a strong opinion or idea?

· Are people afraid of being judged harshly or told their idea is “crazy” or “dumb” in a team setting?

 

Now, that’s a lot of stuff to keep an eye on. (Hey…no one ever said that being the Scrum Master was an easy job.) So, let’s say that you notice something. What do you do about it? How do you head-off fear and/or actually do something about it?

Well, if someone on the team shares a concern or asks for help, be sure to thank them for bringing it up and offer them support, or try to connect them with someone who can. If people are hesitant to speak up in a large group setting, approach them after the meeting, and discuss it in a more casual environment. If they need some encouragement or support, find a way to share their ideas with the team in a less intimidating way. Find ways to bring new team members on-board and make them feel connected quickly. Make sure no one is discouraging open and honest conversation by dominating conversations or by openly criticizing ideas or opinions, even jokingly. Joking, while good natured, can be misconstrued as criticism, and simply telling a teammate that they “just can’t take a joke” is a great way to alienate them and ensure their participation in future activities is limited. Besides, some of the biggest discoveries in history started with an original premise that was totally out there!

I’ve given talks on fear at a number of conferences, and every time people have approached me afterwards saying “I feel that way too. It’s so good to know I am not alone!” Research shows that around 70% of people struggle with these kinds of fears, and based on my experience, it is higher in IT! That means that in any given meeting you attend, MOST of the people in the room are afraid to share their thoughts for fear of negative consequences. Imagine all of the great ideas being squandered and land mines we are failing to avoid.

Hopefully you’re already thinking of ways to improve the quality of your team, and ultimately of the products you are delivering. Strive to be more vigilant, more supportive, more honest, and you will be well on your way to creating a high-quality and high-performing team!

 

If you’re attending quest, I also have a few sessions there that you may want to check out if this article spoke to you.

Getting Your Agile Team Unstuck! Tips and Tricks for Avoiding Common Agile Setbacks: http://qaiquest.org/2017/sessions/half-day-tutorial-getting-your-agile-team-unstuck-tips-and-tricks-for-avoiding-common-agile-setbacks/

Fear and (Self) Loathing in IT: A Healthy Discussion on Imposter Syndrome: http://qaiquest.org/2017/sessions/fear-and-self-loathing-in-it-a-healthy-discussion-on-imposter-syndrome/ 

And if you’re not attending Quest feel free to send me a message via this blog or on Twitter!

0

Join Polaris at the QAI QUEST Conference in Chicago Next Month

by Angela 22. March 2016 12:15

Next month, the Quality Assurance Institute brings the Quest conference back to Chicago. Quest is the Quality Engineered Software and Testing Conference & EXPO, and it’s a fantastic place to network and learn about the latest trends in quality assurance, team collaboration, and software delivery. From the website:

LEARN - ASSESS - APPLY - CONNECT

QUEST 2016 Conference is the best source for new technologies and proven methods for Quality Engineered Software and Testing. Thought leaders, evangelists, innovative practitioners, and IT professionals from across North America gather together for a week packed with classes, tutorials, educational sessions, hand-on workshops, discussions groups, EXPO, and networking events. Let your quest to build, test, and deliver quality software begin with QUEST 2016! You’ll see sessions around topics such as Agile, Leadership, Measurement, Test Design, Automation, Open Source, Performance, Test Data, Mobile, Security, DevOps, And More… Check out the conference schedule here.

Chris Taylor and yours truly will be delivering a number of sessions at the conference including:

 

I’ll also be speaking at the Manager’s Workshop. I’m excited to have an opportunity to participate in this. I’ve attended in years past as an attendee, and it’s an awesome opportunity to network and learn from peers and thought leaders about some of the things we all struggle with in the software business.

I hope you can attend the conference and perhaps even stop by one of our sessions! Register here while tickets are still available.

0

Chicago Code Camp Call for Speakers is Open

by Angela 17. February 2016 08:52

In case you haven’t heard, Chicago Code Camp call for speakers opened last week and we need you! Not heard of Chicago Code Camp? Well, grab a cup of coffee and pull up a chair because we have a great story! This is our 8th year, and once again we’ll be staying in downtown Chicago at the Illinois Institute of Technology to make sure we are centrally located and easy to get to by car, train, or subway. It is a day to learn from the community. It is a day to contribute to the community. Please join us by sponsoring, attending, speaking, or all three! We cannot be successful without you. 

The mission of Chicago Code Camp is to provide a credible resource within the IT industry. Our goal is to offer a wide range of opportunities to learn about advancements in our field, to share knowledge from our experiences, and to develop valued relationships with our peers. To that end, Chicago Code Camp is a FREE, day-long event. We are here to connect the talent and expertise within the Developer community of the Windy City, and that includes YOU. Discussions for the day have previously included development and trending topics in .net, java, open sourced frameworks, web, mobile, cloud, robotics, testing, soft skills, and more.

So what ideas, technologies, or strategies do you want to share with us? Everyone has something to contribute, whether its information on a new JavaScript framework, teaching us how to leverage Docker to strengthen our DevOps practices, sharing experiences adopting scrum, or how to handle ourselves better in job interviews. We are looking for a broad set of experiences across just about any topic related to being a technology professional.

Note on our selection process: In order to be fair towards all the speakers who submit for sessions for the Code Camp, the speakers are chosen via a blind voting process by the Chicago Code Camp Advisory Council (CCCAC). The advisory council is made up of various local and regional user group leaders and industry experts. The council will only see the topic title, abstract, and level of difficulty of the talk when voting for the abstract. The council does not have access to the presenter's information. The abstracts with highest votes are then placed into tracks and presenters are notified.

So take a few minutes to absorb some caffeine, think about some topics you’d be willing to share with the rest of the tech community in Chicago, then submit your ideas here: http://www.chicagocodecamp.com/Submissions/WantToShare

 

Hope to see you at Chicago Code Camp this April!  Oh, and general registration is not open yet, but stay tuned for news on that Smile

0

Last Chance to Register for the CQAA Agile Testing Practices Program on Jan 26th in Chicago

by Angela 25. January 2016 15:54

I don’t run across many non-QA folks that are members of CQAA – the Chicago Quality Assurance Association, which is a shame. If you’re reading this blog, you’re probably part of a software development team (or you are my mom being supportive – Hi Mom!), and ALL members of the team are responsible for quality so really you should check out CQAA in general. They have a lot of really great local events and webinars, AND this year they have a conference coming to Chicago. More on that later…

I coach a lot of software teams on agile and Scrum and hands down one of the biggest challenges is quality.  Specifically – how does QA keep up with development efforts? Well, my first bit of advice is that keeping up with testing implies that only QA is bothering to assure that quality is there, and developers have a huge role to play too. How they do that, well, your team needs to decide. Some level of up-front testing is critical to ensuing quality from the moment there is enough of a requirement worth swarming on to the minute it hits production. TDD, BDD, ATDD, there are many options. This might be just the opportunity you’ve been looking for to delve more deeply into that topic if you’ve been on the fence, or maybe if you haven’t even begun doing the research. Software developers are inherently “lazy” right? How efficient is it that Karen can give you the run down and save you a lot of Googling Smile

This looks like a great event that I hope you consider attending, regardless of your role on the team. I was fortunate enough to end up at a lunch table with Karen many years ago at a Quest conference, and Karen had so much great experience and insight to share. I look forward to any opportunities I can find to learn from her. Today is the last day to register, and I really apologize for the last minute notice but I had forgotten about it myself until today.

 

Influencing your Team Towards BDD & Agile Practices

Karen N. Johnson

About the Topic

We’ve shortened the software development release cycle and we are even moving towards continuous delivery, but our testing efforts still seem to have that waterfall-feel to it. How can we influence more Agile testing practices without feeling like our testing strategies have “fallen off the rails!"

First let’s look at a few of the common terms such as BDD and TDD and understand what each term means and what those practices look like in our daily lives. Next let’s explore small tactical practical ways we can influence adoption of early test thinking on our teams. Let’s also develop a few short concise “elevator pitches” that we can share with teammates, product owners and even senior management in those casual spur of the moment conversations that take place to help influence a continual and evolving adoption of BDD and Agile test practices.

Key Learning Objectives

  • Understand the terms BDD & TDD
  • Learn specific tactics to help move your team towards Agile testing practices
  • Develop an “elevator” pitch for promoting BDD for every layer of management 

About the Speaker

Karen N. Johnson has worked as a software test consultant for many years. Her client engagements range from teaching to project work. Karen is frequent speaker at conferences. She is a contributing author to the book, Beautiful Testing by O’Reilly publishers. She has published numerous articles and blogs about her experiences with software testing. She is the co-founder of the WREST workshop, more information on WREST can be found at: http://www.wrestworkshop.com. Find her on Twitter as @karennjohnson (note the two n’s) and her website: http://www.karennicolejohnson.com.

Host and Location

SAVO Group Ltd.

155 N Wacker Drive

2nd Floor Conference Center

Chicago, IL 60606

Agenda

1:30-2:00 Sign-in & Networking

2:00-2:15 Announcements

2:15-4:00 Presentation (15 minute break at 3:00)

Registration

REGISTRATION IS REQUIRED TO ATTEND THIS PROGRAM.

PLEASE REGISTER BY Monday, January 25, 2016 at www.cqaa.org. If you have any questions, please contact CQAA Program Director at programs@cqaa.org.

 

Hope you can make it! And if you do attend, wave to my husband if you see him, as it is in his office Smile

Tags:

TDD | BDD | Software Testing | Quality Assurance | Quest | CQAA | Software Quality | unit testing | Test Automation | Testing | Agile | Application Lifecycle Management | Scrum

0

Will I see you at St Louis Days of .NET this year?

by Angela 9. November 2015 14:19

St Louis Days of.NET is definitely a favorite of mine. This will be my third year both attending and speaking at the conference, Polaris Solutions is also sponsoring the conference again! Everyone involved is so passionate about the community and great to work with, I’m excited that my company can be a part of it. And for the money, it’s hard to beat these speakers and sessions! Speaking of, I hope you have your ticket because they are SOLD OUT!

Be sure to stop by the Polaris Solutions booth and chat with one of us about ALM, TFS, agile/scrum, and any number of other topics. You can also keep up with all of the STLDODN news and announcements on their website,on Facebook, and of course Twitter. Many of us at Polaris will also be speaking at the event, and posting regular updates on twitter as well. Hope to see you there and on Twitter! Smile

My Sessions:

Friday, 8am in Discovery C

I know it’s early but I’m super energetic so I’ll do my best to kick off the conference in an awesome way for you!

How TFS 2015 is Going to Rock Your Agile world!

If you’ve been using Team Foundation Server for a while, you know it can do everything short of making you a latte as you walk into your morning scrum. TFS has come a long way in the last 10 years, and with the release of TFS 2015 and all of the features being released to VSO at break-neck speed, it’s hard to know why you should consider upgrading or even adopting in the first place. With the release of TFS 2015, Microsoft has laid down some SERIOUS awesomeness with a reboot of Team Build, a ton of new agile based team planning features that will melt even the saltiest scrum master’s heart, and easy integration into collaboration tools like Slack, Hipchat, and Trello with service hooks. And lastly, there are some cool new testing capabilities, some which are open to people with no licensing, yeah, FREE STUFF. Join me for a tour of the best of TFS 2015, IMHO anyway.

 

Saturday, 12:30pm in Discovery D

Yikes, right after lunch! Again, I think my energy will come in handy, have to keep everyone awake, ha!

Deconstructing the Scaled Agile Framework

With so many process frameworks and methodologies out there, it’s hard to know where to begin. And just when everyone seems to be warming up to agile, here comes SCALED agile. But how is SAFe really different than agile? When is it appropriate? Does using the SAFe framework prevent a company from having scrum teams? How big or complex do you need to be for SAFe to make sense? Isn’t SAFe just a glorified version of waterfall that companies adopt when they can’t handle “real” agile? I found myself overwhelmed with choices, and confused by all of the conflicting articles out there on what SAFe was, and how and when to consider using it. I decided the best solution was to go through the training and spend some time practicing it in the field. Since becoming an SPC, I have coached a number of clients on improving their processes leveraging techniques from SAFe. In this session I plan to walk through the tenets of SAFe and help you to understand how SAFe can benefit your team!

 

Find the full detail with speakers and rooms here.

 

Follow us, we’re nice,and we’re on twitter!

Polaris twitter account: https://twitter.com/teampolaris

Angela’s twitter account: https://twitter.com/OakParkGirl

Alejandro’s twitter account: https://twitter.com/alejandrormz

Josh’s twitter account: https://twitter.com/jcgillespie

Chris’s twitter account: https://twitter.com/cbkadel

Clint’s twitter account: https://twitter.com/ClintEd

 

 

All Polaris Sessions

Alejandro Ramirez - Specflow for Agile Teams

Angela Dugan

  • Deconstructing the Scaled Agile Framework
  • How TFS 2015 is Going to Rock Your Agile World!

Brian Yuan - How to Climb the AngularJS Learning Curve

Chris Kadel

  • Introduction to Dev-Ops: 2+2=5
  • Team Foundation Server Building Extravaganza 2015

Clint Edmonson

  • Agile Metrics that Matter
  • Application Architecture Jumpstart

Josh Gillespie - Discover PowerShell DSC

Nathan Gomez - Entity Framework for Non-Sadists

0

Manually Changing Test Configurations in Bulk in MTM –There is an Easier Way

by Angela 12. June 2015 15:56

Another one of those silly little tricks I didn’t realize was available to me until I tried, and I thought I would share, because SURELY someone else out there would need it at some point.

Just ran into a situation where someone created a bunch of test configurations and made it their plan default, then started adding test cases like the wind.  Before we knew it, over 1,000 test points were generated! (175 test cases x 6 test configurations per test case = 1,050 test points) We really only needed one test point per test case, and the last thing I want testers doing is opening every single test and editing the configuration. Hello carpal tunnel! And I could certainly write some PowerShell to fix it too, but heck even that would take a decent time to write, test in a sandbox, run in production, etc. I figured there HAD to be a way we could quickly fix this manually. There were a LOT of test cases but only a few suites that they were all contained in. I’ll use my own test plan as an example of the steps performed to protect the innocent Smile

Here is a test plan that I am going to use as an example. And notice I am in the desktop client (against TFS 2013.4 specifically), there is not an easy way to do this in the web tools that I am aware of. I have a number of test cases with multiple configurations, and let’s say in this case I really just need a single configuration across all test cases for this plan.

image

You can certainly just open each test case and select the appropriate configurations at the test CASE level, but imagine a suite with 100 test cases, that’s a LOT of clicks.

image

Of course we can also do this at the SUITE level, and not everyone knows this is even an option so I’ll call it out just in case:

image

image

So certainly saves you from opening each test case before you can select the configuration, but again, if there are 100 test cases in this suite that is STILL a lot of clicks.

Well, did you know you could use CTRL or SHIFT to highlight multiple, or even all test cases in this view? You do now.

image

At this point, the assumption is that you want all highlighted items to end up with the same configuration.  If you need to change 100 test cases in a suite to different combinations of configurations, well, I can’t really help you.  But if you need to set them all to the same value just highlight all of the relevant ones, click in the last column, and select the configurations you want to set them all to.  If it happens that you need them all back to the plan default, just hit Reset. BOOM!

 

Hope that saves you some aggravation down the road.  Especially if you are not in the position to write PowerShell, as many MTM users are not..

Tags:

ALM | Application Lifecycle Management | MTM | Microsoft Test Manager | Microsoft Test Professional | Quality Assurance | SDLC | TFS 2013 | TFS | Team Foundation Server | Test Case Management | Testing | Visual Studio

0

Still Running TFS 2010? It’s Aging Out of Support Next Month. Polaris Solutions Can Help You Upgrade Quickly

by Angela 4. June 2015 12:04

You heard me correctly, mainstream support for TFS 2010 ends on July 14th, less than 6 weeks from today! So if you’re thinking “it still WORKS, why should I upgrade?” Consider these points…

  • Any issues arising with your server will NOT be patched or serviced by Microsoft support, and it will be harder and harder to find experienced people to work on it (well, who WANT to work on it)
  • Your infrastructure team may be chomping at the bit to stop supporting the old operating systems and SQL Server versions that TFS is running on
  • You’re missing out on some amazing new capabilities that it would take me hours to cover and that I promise will revolutionize the way you develop and deliver software
  • You attract great new talent by offering robust and modern development environments, trust me on this
  • I can tell you from a LOT of personal experience, that the longer you wait to upgrade, the harder and more time consuming it is!

The good news is that you may qualify for up to $5,000 worth of free services to help you plan and prepare for your upgrade through the Microsoft Deployment Planning Services program (DTDPS)! Wondering what that is? Below is a quick FAQ that I created to explain the program:

Now what exactly IS DTDPS? Well first of all it’s a Microsoft offering, so expect MANY acronyms to follow. DTDPS stands for Developer Tools Deployment Planning Services. Specifically, the development tools that these services are meant to be used in conjunction with are the Microsoft Visual Studio ALM platform - Team Foundation Server, Visual Studio, and Microsoft Test Manager (TFS, VS, and MTM for good measure). 

So what does this really do for me? While most people are already very familiar with Visual Studio from a .NET development perspective, many people who own the other tools within the TFS platform are not taking full advantage of them. DTDPS is the solution to this problem, connecting customers with the right partners to make sure they are getting the full value of their ALM investment. Software that sits on the shelf is a huge waste of money.  And from Microsoft’s perspective is something you’re not likely to buy again, so it is of course in their interest to offer such a program.

What kinds of services are included in DTDPS? Currently there are 4 DTDPS offerings available: TFS deployment planning assessment, Visual Studio Quality Tools assessment, Visual Studio Agile Deployment Assessment, and Visual Studio DevOps Deployment Assessment. You’ll notice a theme here, the word “planning”. These engagements are not meant to be used to implement the tools. Instead, they are short, fixed-length (3 and 5 days) engagements for gathering data and analyzing your current environment and needs in order for us to help you build a plan for implementation and adoption of Visual Studio and TFS ALM tooling. It’s a great kickstart and will drastically accelerate your ALM initiatives.

But what if I don’t need one of those services, but need other assistance with TFS? Well, it depends. I know, I know, typical consulting answer. These programs can be expanded upon to assist customers with other ALM related concerns, so drop me a line at the email I provide below, and I’ll be happy to discuss it with you in more detail. 

Who delivers the engagement? DTDPS is a program delivered through certified and experienced ALM partners like Polaris Solutions to help customers with SA (Software Assurance) benefits to take full advantage of the tools they own.  We have delivered dozens of these engagements over the past few years and every customer we have worked with has been extremely happy with the valuable roadmaps that we delivered. You will benefit from a wealth of relevant experience and proven ALM practices that only comes from us having deployed and leveraged the tools in a large number of different environments and business verticals.

OK, I’m intrigued, but how expensive is it? It is FREE. Seriously, and absolutely.  This benefit is available to customers who purchase Microsoft products with SA, think of it as a rewards program. In fact, you may have DTDPS credits without knowing it!  Many of the customers I work with did not know they had DTDPS credits available until I turned them onto the program.

I want in! How do I sign up?  Start at the DTDPS site. Here you can peruse the various services available and see which ones are right for you and your organization.  Then check out the DTDPS QuickStart guide which walks you through the steps of accessing your benefits.  Then you just pick a partner to work with, like us, and you’re on your way to a better way of doing ALM!

 

If you are interested in learning more about DTDPS, or if you would like to find out more about getting a free quick assessment of the effort required to upgrade and the benefits that your team would enjoy, please contact me at Angela@PolarisSolutions.com. And if you know anyone still using an older version of TFS (anyone running TFS 2013 or earlier qualifies) help them out and point them to this blog!

0

Polaris Solutions Holding an ALM Lunch and Learn on Agile Testing Success in St Louis Next Month

by Angela 24. February 2015 14:39

    Our St Louis office is holding a Lunch n Learn at the local Microsoft office in March. Agile testing is a challenge for most software teams, especially larger organizations with well-established QA groups and processes. Learn from one of our resident agile testing experts at the free event!

    More details:

    Description: If you are either planning to or are already practicing agile software development, Team Foundation Server (TFS) and Microsoft Test Manager (MTM) offer you a powerful platform to successfully plan, manage and execute agile testing.

    During this free lunch session we will cover in detail the different testing capabilities offered by TFS 2013 and MTM for Scrum and Agile methodologies, and will also share what we have learned from helping our clients as they implemented and matured their agile testing practices.

    Key Experiences:

    • The evolved role of testing in Agile Projects

    • Iteration test planning techniques

    • Test tracking with TFS and MTM

    • Different approaches to bug management

    • Test automation Do’s and Don’ts

    • Testing metrics that are worth measuring

    • Exploratory testing strategies

    • Best practices & lessons learned in the field

      Complimentary lunch will be provided to registered attendees.

      Presenter: Alejandro Ramirez is a Software Quality professional and Senior Consultant with Polaris Solutions. He has over 17 years of experience working in software in development, testing, and IT governance. His experiences range from small businesses, startups and non-profits, to Fortune 500 corporations in a variety of fields. He is certified in ITIL and Lean. He is also a blogger, speaker, mobility champion, and helps companies incorporate ALM strategies to continuously deliver valuable software.

      When: Tuesday, March 24, 2015 from 11:30 AM to 12:30 PM (CDT)

      Where: Microsoft Corporation, 3 Cityplace Drive Suite 1100 Creve Coeur, MO 63141

       

      Register for this Polaris Solutions event today!

      0

      Referencing and Copying Test Cases in MTM 2013, a Lesson in Patience

      by Angela 22. August 2014 15:49

      Recently, I’ve had some lengthy discussions about test case, suite, and plan copying in Microsoft Test Manager (MTM), and it something that a lot of people are struggling with. In some cases, people are not even aware that you can do all of these things, let alone the subtle differences around what they are doing behind the scenes. Either way, hope this sheds some light on another way that MTM helps you to manage your testing efforts. There are a handful of methods for reusing test cases across multiple test suites and plans.

      1) Add existing test cases – also known as re-using a test case by referencing it. So, in MTM, test cases are by default REFERENCED when you add them to test plans/suites.  You do this through the Add button in the Plan tab of MTM.

      image

      The implication for using Add is that you need the EXACT SAME test case in multiple places, and if the test case changes it needs to change everywhere. So if I add a test case to 3 different test suites, any change to the test case is reflected in all 3 places automatically. Think of the test case instances that you see in the suites as pointers back to the original test case. Handy! Or annoying depending on your test versioning strategy. As an added bonus, with Add you can pull in test cases from any test plan in the team project collection by simply removing the @Project clause on the query!

      image

       

      2) Create test suites by referencing existing test cases performs a shallow copy of test suites from a different test plan within the current team project, allowing you to easily reference its test cases. There are 2 places where you will find this option, in the context menu of the Test Plan, as well as in the MTM menu bar of the Plan | Contents tab.

      image

      image

      In MTM 2010, this option was called “Copy test suites from another plan” , which to most reasonable folks sounded like it copied everything. But it was not really a full copy of everything, it was actually a brand new test suite based on the original suite, and the suite contains REFERENCES back to the original test cases. As you can see, in MTM 2013, the menu option is now more explicit about what it is doing. The brand new suite has a new ID and the same name as the original test suite, it also includes all of the original test cases but is just referencing the test cases and their associated requirements. Changing the new test suite does not affect the original suite, but remember that changing the test cases in the new test suite would change the test cases in the original test suite. Also, note that this can only happen across different test plans in the same Team Project, so you cannot use this feature to duplicate test suites into the test plan you are currently in, or to duplicate test suites across Team Project boundaries. Maybe that is an edge case, but people have asked me if they could do it.

      But what about the cases where you really do need to effectively BRANCH those test cases?  Say you have a new version of some functionality, but you still need to support the original functionality, and so you need to have two slightly different versions of the same test case. Well, you have yet another option – Copy. Technically you have a few more options yet.

      3) Create copy and add to suite is a shallow clone operation on just a single test case. Accessible in the MTM client, you just right click on any test case, and use this tool to create a new copy of the test case, and save it into the test suite that you are currently in. All links, comments, steps, parameters (shared and otherwise), and properties are carried over - but new versions of all of these related items were not created. The new test case refers back to the same links, parameters, etc. of the original test case, and even links back to the original test case so you can see how it originated. Test run results associated to the test case are NOT copied over. Attachments are NOT copied in this case either. And again the scope is the current Team project, current test plan, and current test suite. I cannot cross Team project, test plan, or test suite boundaries with this command.

      image

      But we’re not done!

      4) You might have noticed a Copy (CTRL + C) option in that context menu in the MTM desktop client as well. Don’t be fooled, this just creates another reference to the original test case wherever you paste.  So while it is similar to using the Add button, I can only Copy a test case using this command into another test suite within the same test plan. In other words, it does not work across Team Project or Test Plan boundaries, but it MUST be used across test suite boundaries. And in this case, Copy actually means reference, instead of you know, copy. I know, really? OK, one more option to cover in this blog post.

      5) Create a copy of this work item (including links) is the Copy option available only on the web, and it is slightly different than the options available in the desktop version of MTM. This appears to just be the standard Copy Work Item context menu option that you can access anywhere on the web, and nothing specific to the test tools. Clear as mud, right?

      Honestly, I’m also having a hard time understanding how it is SUPPOSED to work because it has some odd behavior in my opinion (on VSOnline anyway). It allows you to specify a “Project” in the creation dialog, which I assume means TEAM PROJECT, like it does when you are creating copies of any other work item type from the web. The new test case work item is created in the specified project, with the same references as the original work item, but also adds it to the existing test suite in the current project. I assumed it would only create the new test case in the team project specified. Apparently not. So it does the same type of copy that Create copy and add to suite does, but allows you to do it across team project boundaries. image

      image 

      Frustrated yet? I know I am and I’ve been using these tools for years. It’s a lot to keep straight, and even I sometimes forget which options bring over which links and artifacts so I have to refer back to the handy tables available on MSDN.  Definitely talk to your team and decide which options to use and when.

      Oh, yeah, and cloning is also an option now, but that is another larger discussion so stay tuned for another blog post on that one.

      0

      TFS 2013.3 CTP – What I’m Most Excited About: Part 1

      by Angela 4. June 2014 19:57

      Did you hear that there is a CTP of TFS2013.3? In case you missed Brian’s blog post, there is some really great stuff in there! I’m really jazzed about the big, BIG changes to Test Plans and Test Suites. They’re now work items! Now, in case you’re not sure why this is a big change, in the past Test Plans and Suites were not items you could customize or query, like you could Tasks, Bugs, etc.

      The first step is upgrading.

      image

      The process is very similar to every other upgrade or update you’ve applied. So pretty darn easy. Fortunately, it’s also a super fast process.

      image

      Took under 15 minutes from start to finish for me, although admittedly I have a fairly small implementation with just 2 Team Project Collections and a handful of Team Projects on each. A *lot* is happening behind the scenes, including some major data transformations, so if you plan to take on this update when it releases it would be a GREAT idea to run the upgrade against a clone of your full production databases in a test environment. Not only to get an idea of the time it will take for your production upgrade, but to ensure you don’t encounter any unexpected issues. Particularly if you are heavy users of Test Plans, Test Suites, and Test Case work items. You can use these backup and restore instructions to create a test instance of your collection databases. And since I was updating from TFS 2013.2. there wasn’t even anything to configure once it was done for everything to work, just update and go!

      Be sure to download it here and install it, but not in production eh? It’s not a go-live, but it’s worth checking out on your own instance of TFS :) I’m currently testing out all kinds of new features available to me, and will be sure to post a few follow-ups to this post detailing why this update will rock your world soon!

      Powered by BlogEngine.NET 2.7.0.0
      Original Design by Laptop Geek, Adapted by onesoft