V3.3.0 dev

[jwildfire]

All Feature branches merged. Ready for regression testing.

[danedexF5]

Regression Tests

Filters and Options

• [x] * Confirm that clicking on the "+" to the left of each category name expands the dataset
• [x] * Confirm that clicking on the “-“ to the left of each category name after it is expanded collapses the dataset
• [x] * Type a value into the search box and confirm that the table updates to only show the categories that match the search term. Matching terms should be highlighted in bold, regal orange.
• [x] * Confirm that the number of matching terms displays to the left of the search box
• [x] * Delete the entered value from the search bar and confirm that table resets
• [x] * Confirm that filters on events (e.g. Severity) are working as expected by filtering and then clicking on a category to display the underlying data listing to confirm that the data displayed matches the filtering
• [x] * Confirm that entering a minimum prevalence will filter the data based on the entered threshold
• [x] * Confirm that summarizing by 'participant' displays the number of participants who experienced an AE of the corresponding category by group
• [x] * Confirm that summarizing by 'event' displays the number of events of the corresponding category by group
• [x] * Ensure that the aeexplorer looks good in CAT
• [x] * Confirm there is no column overlapping when bootstrap is toggled off/on
• [x] * Confirm that the "Filter by prevalence" field no longer accepts letters in the prevalence input, and that the up and down buttons work as expected - NOTE: This is slightly different in all browsers. Jeremy has stated that it isn't an issue that should stop a release from moving forward
• [x] * Confirm that the graphic updates after each keystroke in the search and filter by prevalence inputs (instead of after focus leaves the input altogether)
• [x] * Confirm that if there are no AEs that match the current filters - the error message thrown says "Error: No AEs found for the current filters. Update the filters to see results."

Hovering

• [x] * Hover over a value in a treatment group to see the number of participants affected out of n
• [x] * Hover over a value in ‘AE Rate by group’ to see the percentage of participants affected by group
• [x] * Hover over a value in ‘Difference Between Groups’ to see two treatments compared and the overall difference between them. This will also highlight the bar containing the value in gray and reveal the count and percentage of both groups under their treatment name
• [x] * Hover over the ‘E’ superscript beside one of the filter labels to display an explanation of an event filter
• [ ]

  Detailed Listing

• [x] * Confirm that you can view a detailed listing of events by clicking on the category name of a given row in the table
• [x] * Confirm that the ‘Return to the Summary View’ button brings you back to the original summary view.
• [x] * Confirm that the section labeled ‘The listing is filtered as shown:’ displays the filters that were selected in the original summary view
• [x] * Confirm that there is a sentence in the header stating ‘Details for x category name records’ that displays both the correct ‘x’ value for the number of records in the listing and ‘category name’
• [x] * Ensure details listing appears as normal before adding anything.
• [x] * Add a details object, like in the example above, that has columns with and without a label and ensure that they show up by themselves and with the proper label when you view the details listing (see this issue for an example of labels: https://github.com/RhoInc/aeexplorer/issues/105)
• [x] * Confirm in CAT with the following settings: { defaults:{webchartsDetailTable:true}} that the detail table view (accessed by clicking the label of any row in the summary table), is rendered using a webcharts table, and that sort, search, pagination and export work as expected.

Downloading Data

• [x] * Confirm that entering the following settings in the CAT will show the option to download the data file: {"validation": true}
• [x] * Confirm that when downloading a CSV, the file will save as major term - minor term - participant/event
• [x] * Confirm that when downloading a participant CSV, "participant" appears in the title
• [x] * Confirm that when downloading an event CSV, "event" appears in the title
• [x] * Confirm that filtering the data will appear as filtered in the CSV download

Settings

• [x] * Confirm that the following settings set the serious event filter to ‘Y’ and make it the only filter to be displayed by default: {"validation": true ,"variables": {"filters": [ {"value_col": "AESER" ,"label": "Srs?" ,"type": "event" ,"start": ["Y"]} ] } }
• [x] * Confirm that the following settings summarize the data by participant on default: {"validation": true ,"defaults": {"summarizeBy": "participant"} }
• [x] * Confirm that the following settings summarize the data by event on default: {"validation": true ,"defaults": {"summarizeBy": "event"} }
• [x] * Confirm that the following setting only shows treatment group totals and hides the 'Difference Between Groups' column:
• [x] {"defaults":{"totalCol":true,"groupCols":false}}
• [x] * Confirm that the following setting only shows the placebo group and hides the 'total' and 'Difference Between Groups' columns:
• [x] {"groups":["Placebo"]}
• [x] * Confirm that when grouping by RACE, yellow is no longer the color that appears
• [x] * Confirm that adding 2+ values to each component (id, major, minor and groups) of the variableOptions array adds a new control.
• [x] * Confirm that multiple filters are created if more than one variableOptions array is provided, and that they both work as expected.
• [x] * Confirm that the new variableOption controls work before and after filtering, searching, and changing the summarizeBy option.
• [x] * Confirm that the value for the default variable appears in the variable control even if it is not specified in config. That is, ARM appears in the groups control with these settings: { variables:{group:"ARM"}, variableOptions:{ group:["RACE","SEX"] }, };
• [x] * Confirm in CAT that margins are drawn for the dot plot when plotSettings.margin is specified. Just tweak the following settings object, and confirm that the margin changes as expected: {plotSettings: {margin: {left: 40, right: 40}}}

[emmorris]

Team discussed the different behavior in each browser and agreed that even though each browser handled it differently we should still pass the step about: Confirm that the "Filter by prevalence" field no longer accepts letters in the prevalence input, and that the up and down buttons work as expected. Chrome doesn't allow the letter to be entered at all. Firefox removes the letter and puts a red box around the field when you click out of it. IE removes the letter after you click out of the field.