Test Outcome on TFS 2010 Cube displaying Point Count Trend with negative value?

Unanswered Test Outcome on TFS 2010 Cube displaying Point Count Trend with negative value?

  • Monday, April 16, 2012 2:38 PM
     
     

    Test Outcome Trend report in excel using the OLAP Cube seems to be having an issue where in “failed” outcome is displaying negative count when the "State" of the Test Case is excluding “Closed” and including “Design or Ready”.

    I am trying to debug the issue & this scenario where the Point Count Trend is reporting a negative count \ value.

    I would like to understand the interpretation of negative value in the outcome for the point count trend. Is this an expected behavior because there was a test case which was run once with outcome "failed" but later the test case status has been marked closed? Or Is there some incorrect sequence of steps followed here whilst using MTM which should be avoided, so that the ETL doesn't populate cube with negative point count trend?

    Thanks & Regards,
    Parag

All Replies

  • Wednesday, April 18, 2012 8:20 AM
    Moderator
     
     

    Hi Parag,

    Thank you for your question.

    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.

    Thank you for your understanding and support.

    Best regards,


    Lily Wu [MSFT]
    MSDN Community Support | Feedback to us

  • Wednesday, April 18, 2012 4:23 PM
    Moderator
     
     

    Hi Parag,

    While you debug this issue, did you try to collect log of reporting service?  If no, you could follow this blog to collect log and troubleshooting reporting service issues. http://weblogs.asp.net/akjoshi/archive/2008/07/09/Troubleshooting-sql-server-reporting-services.aspx

    A snapshot of the test result in report would help people understand your situation.

    thanks and regards,


    Forrest Guo | MSDN Community Support | Feedback to manager

  • Friday, April 27, 2012 4:34 AM
     
     

    Hi Forest,

    You are right I should have provided the snapshot of the issue, because this is not on the SSRS report but just on the Excel Pivot table based report created on the TFS 2010 OLAP Cube.

    Please find the all the snapshots attached for your reference and also the repeated issue definition

    Test Outcome Trend report in excel using the OLAP Cube seems to be having an issue where in “failed” outcome is displaying negative count when the "State" of the Test Case is excluding “Closed” and including “Design or Ready”.

    I am trying to logically debug the issue & this scenario where the Point Count Trend is reporting a negative count \ value.

    I would like to understand the interpretation of negative value in the outcome for the point count trend. Is this an expected behavior because there was a test case which was run once with outcome "failed" but later the test case status has been marked closed? Or Is there some incorrect sequence of steps followed here whilst using MTM which should be avoided, so that the ETL doesn't populate cube with negative point count trend.

    Any inputs to understand this issue better are very much appreciated.

    Thanks & Regards,

    Parag.

  • Tuesday, May 01, 2012 5:00 PM
     
     
    
    
    

    We are having a simular issue with a SSRS report

    the following member returns -1 for a couple of suites where all tests have in fact passed

    Member [Measures].[Failed] AS

      (

         [Test Result].[Outcome].&[Failed],

         [Measures].[Point Count Trend]

    )

    This looks like it may be the same issue as I did see one Test Case in the Design State while all the other were in the Ready state.  I updated that one test case and it still returns a -1 after the cube was rebuilt.  Do I have re-run that test case to get it to update?

    Any and all help would be great

    Brain

    

    Brian Jon Hopenwasser MSTS: TFS 2010 Admin MSTS: TFS 2005 Developer

  • Wednesday, May 02, 2012 9:14 PM
     
     

    I opened a pport ticket with MS and the first step they adviced me to do it a complete rebuilt of the cube via the TFSConfig command with the AnalysistServices parameter set

    
    

    Where you stop the SSRS and TFSJobAgent Service before you run the command, this command can take a long time depending on the amount of Data you have.

    I will not be able to run this for a few days as it takes all reports off line and we have some critical jobs (TFS Agent Jobs) that run as well, so I do not I'll get to until next week sometime.

    I'll give an update when I know more

    Brian


    Brian Jon Hopenwasser MSTS: TFS 2010 Admin MSTS: TFS 2005 Developer

  • Tuesday, May 08, 2012 9:32 AM
     
     

    Hi Brian,

    Good to know that someone else has hit  this kind of issue. I will be waiting to hear if the cube rebuild fixes this?

    Thanks & Regards,

    Parag.

  • Monday, May 21, 2012 2:02 PM
     
     

    Okay

    After a long delay due to some red tape and other company business, I finally got around to running the TFSConfig SSAS rebuild. 

    The Rebuilt did not fix my issue of the -1 being returned for Failed test points trent count when those test suites have no failed test cases.

    I will continue to work with MS Support to try to resolve this and get back to you.  But I will say none of our current Test Plans and/or Sutes are showing this issue therefore we may drop the issue all together as it is not big enough to chase down for now

    Sorry I am not of more help

    Brian


    Brian Jon Hopenwasser MSTS: TFS 2010 Admin MSTS: TFS 2005 Developer

  • Monday, May 21, 2012 2:29 PM
     
     

    Hi Brian,

    Thanks for the update. I will still be waiting to hear from you about the resolution you get on this one working with MS?

    Do drop a mail off-line when ever you get some progress on this issue.

    Thanks & Regards,

    Parag.

  • Tuesday, May 29, 2012 1:13 PM
     
     

    Update:

    MS support has reached out to the Dev team and they have a ticket or two already open with the exact same symptoms.  This points to a bug but as usaul with bugs it could take a while to isolate a fix. 

    I'll try to keep this update to date, but you may want to open a support ticket up as well, you'll get the hotfix much quicker that way. 

    Plus it may help them pinpoint the issue with more cases to look at, and lastly I do not think they charge for support on Bug issues well at least they don't change us but I not sure it that is cross the board thing or what.

     Brian

    
    

    Brian Jon Hopenwasser MSTS: TFS 2010 Admin MSTS: TFS 2005 Developer

  • Monday, May 13, 2013 12:17 PM
     
     

    Hi Brian,

    Did you get update from MS support? I am having the same problem.

    Thanks

    Mark

  • Thursday, May 16, 2013 7:29 PM
     
     

    Hello Mark

    We ended up have to do a complete delete of the warehouse and cube and rebuilt them.  By complete delete I mean we physically deleted the DBs from SQL Server using SSMS, after use the TFSConfig.exe to rebuild them.

    Depending on the size of you DB and hardware you running this effort can take a very long time.  Our Collection DB (we only have on collection) is around 100+ GB and we have a "beefy" SAN attached Data tier with 64 GB RAM and 4 CPU, and it took 8+ hours to run.  During this time all Reports are off line, more over some of the Data changes as well such TeamProjectSK

    Hope this helps

    Also, I wrote a quick PowerShell script to ping the warehouse.asmx to see if the AAIS jobs are running and email me the results,  helped me track it while it was running

    Brian


    Brian Jon Hopenwasser MSTS: TFS 2010 Admin MSTS: TFS 2005 Developer

  • Friday, May 17, 2013 2:21 PM
     
     

    Hi Brian,

    Thanks for posting the update with the resolution which worked for you. AS you have noticed, there was no response from MS on this issue. I have now moved on from that project, But in my scenario, client couldn't afford the downtime since there are geographically time zone separated global development teams. Else a complete re-build of the cube was the ultimate option I was planning to try. Client was more than happy to ignore that one report and that one particular set of data as -vely reported.

    Cheers,

    Parag.