771123 - Connect UI changes with middleware for Top Crashers by Build Date

Status: VERIFIED FIXED

(Socorro :: Webapp, task)

Description

[Schalk Neethling [:espressive]]

Connect UI changes with middleware for Top Crashers by Build Date. See bug 757822 for reference.

Comment 1

[[DEACTIVATED] Adrian Gaudebert]

Associated middleware bug is bug 761609.

Comment 2

[Schalk Neethling [:espressive]]

[:kairo] So, for TCBy Build Date, we want to display all of the table columns currently displayed on TCBS?

Comment 3

[Robert Kaiser]

(In reply to Schalk Neethling [:espressive] from comment #2)
> [:kairo] So, for TCBy Build Date, we want to display all of the table
> columns currently displayed on TCBS?

Yes, same data in the UI for both.

Comment 4

[Schalk Neethling [:espressive]]

(In reply to Robert Kaiser (:[e-mail]) from comment #3)
> (In reply to Schalk Neethling [:espressive] from comment #2)
> > [:kairo] So, for TCBy Build Date, we want to display all of the table
> > columns currently displayed on TCBS?
> 
> Yes, same data in the UI for both.

Was just thinking, do we want to include the correlations column or do we want to leave that one off for now until it has been reworked?

Comment 5

[Robert Kaiser]

(In reply to Schalk Neethling [:espressive] from comment #4)
> Was just thinking, do we want to include the correlations column or do we
> want to leave that one off for now until it has been reworked?

Hmm, good question. I guess you could leave it out possibly. We'll want those somewhere in the future, but I guess we don't have them atm.

Comment 6

[Schalk Neethling [:espressive]]

(In reply to Robert Kaiser (:[e-mail]) from comment #5)
> (In reply to Schalk Neethling [:espressive] from comment #4)
> > Was just thinking, do we want to include the correlations column or do we
> > want to leave that one off for now until it has been reworked?
> 
> Hmm, good question. I guess you could leave it out possibly. We'll want
> those somewhere in the future, but I guess we don't have them atm.

Ok, then one last question I think ;) I guess we also want the byos report to be able to show crashes by build date.

Comment 7

[Robert Kaiser]

(In reply to Schalk Neethling [:espressive] from comment #6)
> Ok, then one last question I think ;) I guess we also want the byos report
> to be able to show crashes by build date.

I don't know of any separate report there, but topcrashes by build date should have that OS selector as well, yes.

Comment 8

[Schalk Neethling [:espressive]]

Navigate to top crashers

At the top of the page there should be two links, By Crash Date and By Build Date.

Choose a version from the drop down that is not a beta, aurora or nightly such as 15.0.1 and then navigate to top crashers again. You should now only see the By Crash Date link.

Select a version that is either a beta, aurora or nightly and head back to top crashers. Click on By Build Date. Once the page has reloaded, you will notice that the correlations column in the table has been removed, this is intentional.

While on by build date, select 3 days and the plugin crash type. Once reloaded there should be a total of 30 crashing signatures, note I am using Firefox 18.0.1. Now click on By Crash Date again, this time there should be 144 crashing signatures.

Lastly, while still on by crash date, click on Linux, there should be a total of 3 crashes. Next click on by build date, after the reload, there should be no results.

That I believe is that.

Comment 9

[Matt Brandt [:mbrandt]]

Attachment: qa - verified

Verified on stage -- 

* The top crasher reports behave correctly when applying filters to them (Type, Days, OS)
* Drilling down into the data after applying the filters also looks correct
* When viewing the top crashers report for nightly, aurora, and beta the option to filter "By Build Date" correctly appears. When viewing RC releases the option is not present