Archive: 10 Reasons Microsoft Test Manager rocks!

  • This article was originally written in September 2014.  It is being reposted here as an archive.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Because I have some insane super power to break stuff, my role on recent projects has been quality and testing (or as I like to call it, driving my developers insane). One of the most popular tools for testing and writing test scripts is currently Microsoft Excel or Microsoft Word.

However, I have been using Microsoft Test Manager for the past 3 years and I absolutely LOVE it! I think anyone that has developers that use TFS for work management should use Microsoft Test Manager, and here’s why:

  1. Traceability.
  • Test Cases can be traced to User Stories (Requirements) which can be traced to Tasks. Which means you can make sure that all of your tasks that meet your requirements have been tested.  You can also make sure that your system is thoroughly tested with Configurations, where you can set different browser and operating system configurations, but use the same steps to ensure that users are doing exactly what they are supposed to be doing in a consistent way across browsers.
  1. Better Communication from tester to developer.
  • Bugs entered from a test run are detailed with each step a tester took up to the moment he entered the bug, and copied automatically to the bug from the test script. These bugs are linked to the test scripts so that you can easily re-test once the bug has been resolved.
  • Let’s face it, end users aren’t the most detailed when something breaks. But with Test Manager, you can see the steps the tester took, what applications they’re running on their machine, what browser they are using and what operating system. Plus they have the ability to add notes and print screens!

TestManagerImage1-Tests

  1. Tests can be recorded.
  • Visual proof of what the tester did! How can it get any better than that? Now you can see exactly what the tester typed or clicked (or didn’t click).
  • The Action log details every mouse movement the user took, what Search term he entered and what he “actually” clicked.

TestManagerImage2-Tests

  1. System Information is attached to tests.
  • When you run the tests through Test Manager, you get a nice little xml file with the testers system information that shows you what browser the user is in, what operating system, etc.  This can be a great tool if your developer is unable to reproduce the bug on his machine.

TestManagerImage3-Tests

  1. Shared Steps RULE!
  • On my current project, we have over 200 test cases, with a lot of similar steps, but with different security requirements. As with most projects, we had a couple (hundred) requirements changes, which means test cases had to change. Shared steps means that you only have to make that change in one place and it will automatically be reflected in all the test cases that use that shared step.
  1. Create End User Test Script Document with Export to Excel
  • If you don’t have licenses to allow your testers to test in Test Manager, you can still write the scripts in Test Manager and export them to a format end users love…Excel
  • Thanks to the brilliance of my coworker, Jonathan Rupp, I am able to export all my test scripts into a beautiful format on my Windows 8.1 that includes formatting and shared scripts.  He has taken the Export to Excel  tool I found on codeplex for my Windows 7 machine and improved it a quite bit in order to include shared steps and html formatting and be compatible for Visual Studio 2012/2013 and Windows 8/8.1.
  •  I could never use Shared Steps in the past because I knew that I had to export my test scripts to Excel for end users that did not have the licensing to use Test Manager, but thanks to the upgrades in the Export to Excel tool, I can.
  • You can find that awesome tool here: Export Test Cases to Excel

TestManagerImage4-Tests

  1. Create a Detailed Test Plan by Exporting to Word
  • You can also export all of your test scripts to provide you’re a very user-friendly Test Plan with Test Scribe.   It details all the important information about your test plan including configurations, your Suite Hierarchy, Test Case Steps, etc.  It’s a Visual Studio add-on that you can get here.

TestManagerImage5-Tests

  1. There are two options to run tests in Test Manager
  • On the desktop application – which is my preferred way because it is the only way to turn on the recording while testing.
  • Via the browser – which gives you less functionality, but is easier for an end user to test without having to download test manager on their machine.
  1. Organizing Testing Sessions is a snap
  • You can use Suites to create a folder and use the “Add” button to search for test scripts to add to that folder, or create a Query Based Suite based that automatically puts all test scripts that meet a certain query in a suite.
  • For Example, for Round 1 of testing, we had testers testing certain components, so we created Suites (much like a folder), that were called that component. For Round 2 we are testing based on User Role, so we named the Suites with the user role. Users don’t have to search through all the test scripts, they just go to their Suite, or if you’re printing, you just print that suite for them.
  • For manually created Suites, you can set the order of the test scripts, to allow a user to test steps in a specific order, and you can change the order at any time.
  1. Test scripts can be automated
  • I haven’t personally done this yet, but I hear that it’s true. If you record a user walking through the test script, you do some sort of magic mumbo jumbo (coders call it programming) to turn it into an automatic test. You can find more information about that here: Creating Automated Tests

 

Archive: Page Views in 0365 SharePoint Online

This article was originally written in September 2014.  It is being reposted here as an archive.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I worked on a project where I created an “ad hoc” catalog.  The client wanted to have a Document Center that is private to them, where they can publish deliverables, such as Word and Excel documents, but have them displayed on a page in a separate site collection that their client has access to.

We created a Document Center, added a Document Library and checked the box to make the library a catalog…which means, users can have access to the content, without having to give users access to the source library.  Ben Niaulin does an excellent job of explaining what it is and how to do it here.  http://en.share-gate.com/blog/migrate-sharepoint-2013-what-is-product-catalog .

The client-facing site is 1 landing page with introductory text and links, and 1 page with 4 Search web parts (1 Search Results Web Part and 3 Content Search Web Parts) and uses Managed Navigation to determine what should be displayed on the page.   As a user clicks on a term in the navigation, the page refreshes to display items that are tagged with that term.

We got the site up and running and things were going beautifully.  Then my client asked for a report to see how many times their client has accessed the site.  Great!  I know that SharePoint 2013 has a content viewing report that I can quickly run and get my client the information they need.

Unfortunately, I found out the hard way, that this function does not work in SharePoint Online.

Available audit log reports

Content viewing    Reports users who have viewed content on a site. In SharePoint Online, this report will be blank as these events are not captured during auditing.

http://office.microsoft.com/en-us/sharepoint-help/view-audit-log-reports-HA102772739.aspx

Argh!  Trying to figure out what I CAN report on, I discovered that what I CAN do, is run a report that tells me how many times a Search Query was run.   Every time a user opens the Deliverables Page, four search queries are run, one for each Search web part on the page.  All I need to do is group the 4 “events” as one and that will tell me how many times the user has opened the page.

The downfall is, that I can’t tell “which” documents the user is looking at, but we just needed to know that the client was opening the site at all, which this report told us they were not.

Instructions to Generate a Deliverables Page View Report

  1. Review Past Page Views on client-facing site
  2. Navigate to the Site, Site Settings
O365 Site Settings

O365 Site Settings

  1. Go to Site Collection Administration, Audit Log Reports
O365 Audit Log Reports

O365 Audit Log Reports

  1. Scroll to the bottom of the list of reports and select “Run a Custom Report”
O365 Run a Custom Report

O365 Run a Custom Report

 

  1. Select a folder in the SharePoint site to save the report to, select your dates, users and select the option for “Searching site content”.   You can also select the “Opening or downloading documents…”, but it does not currently work in SharePoint Online.
O365 Run a Custom Report Not Working

O365 Run a Custom Report Not Working

  1. Click OK.  The screen will refresh and give you a confirmation message with a link.  The link may not work.
O365 Operation Completed Successfully

O365 Operation Completed Successfully

  1. After clicking on “Click here to view the report, you may see this:
O365 Something Went Wrong

O365 Something Went Wrong

 

  1. If it does not, navigate to the folder you saved the report to in the previous step, right click on it and “Download a Copy”.  Then open Excel and open the report.
O365 Site Contents

O365 Site Contents

 

O365 Download Report

O365 Download Report

  1. At the bottom of your screen, you will see an option to save the file, which will copy it to your c:/downloads folder, or you can click on the Arrow next to “Save” and select “Save As” to choose your own location.
O365 Save As from Downloaded file

O365 Save As from Downloaded file

 

  1. You should see a confirmation that the file has been downloaded with a link to open it
O365 Downloaded File Confirmation

O365 Downloaded File Confirmation

 

  1. Click on the Report Data 1 Tab
Excel Report Data Tab

Excel Report Data Tab

 

  1. Change the format of the “Occurred (GMT)” column to US Date with Time (US is the only one that will allow both Date and Time, which is very important for the next steps.
Excel Format Date

Excel Format Date

  1. Because the page has four search web parts on it, every time a user opens it, he or she will generate 4 search “events” that are logged on the report.  So 4 lines = one page view each time the page is loaded or refreshed on my page.  Your number will be different if you have a different number of search web parts on the page.  In my example, I can delete the 2nd through 4th of each duplicated item with the same time stamp.
  • Be careful though, if there are 8 during the same time, the user navigated to another term within the same 60 seconds
Excel View Report

Excel View Report

 

  1. Additional clean up includes hiding columns that are not needed and using Ctrl+F to Find and Replace everything within the <*> to remove the userID information to leave the nice formatted name in the User Id Column.
Excel Cleaning Up Report

Excel Cleaning Up Report

 

Cleaned up version of the report:

Excel Cleaned Up Version of the Report

Excel Cleaned Up Version of the Report