AMP 2016.3.0 Release Notes
| SSB ID | Component(s) | Detailed Release Note |
|---|---|---|
| US1627 | Manual Testing Mobile |
When a mobile test type was created in AMP, the manual testing tree was not automatically populated with mobile Best Practices, unless the test was created via AMP for Mobile. The manual testing tree has been modified so it always displays relevant mobile Best Practices when the testing type is iOS or Android. |
| US1667 | Automated Testing User Interface & Experience |
The "Testing in Progress" pane showed a maximum of 2 spiders that were in the queue. The pane will now show all spiders that are running or in the queue. |
| US1593 | Automated Testing Performance & Scalability | Increased usage of AMP has lead to some of our hosted clients experiencing delays when their spiders are running, as only 2 spiders could be run on each AMP instance at any given time. Improvements have been made to the spidering process to allow it to scale to meet current demand. For our end users this change will be noticed when initiating a spider. If others hosted on the same server are running spiders at the same time, the new spiders should no longer be queued. Rather, they will run as soon as they are initiated. |
| US1607 | Integrations Reports |
A new JIRA Integration add-on product is now available for AMP. This product allows organizations to link their AMP instance to their JIRA instance. Users with the proper permissions will be able to select violation instances in AMP and create issue in JIRA for the selected violations, directly within the AMP environment. For more information, please email sales@ssbbartgroup.com or contact your SSB account manager. |
| US1628 | Alchemy | When Alchemy had an available fix for a violation, users only had the option to use the fix or pass the violation. Per user feedback we have added more options for these violations. The tester can now choose to use the Alchemy fix or to pass or fail the violation instead if they wish to fix the violation themselves directly in the source code. |
| US1629 | Alchemy User Interface & Experience |
Alchemy now displays to testers the total number of fixes already defined for the page being tested and an indicator to let the tester know whether or not the page being tested already has fixes deployed. This allows testers to know when they are testing if the fixes they specify will be automatically deployed when they are saved. Additionally, testers can now filter the list of violations in the automatic testing mode by their status -- Marked for review, Passed, Failed or Fixed. |
| US1606 | Organizations User Interface & Experience |
When an AMP user had any role other than Organization Administrator for any organizations, the user was unable to see the "Organizations" navigation menu when they were in any of the organizations in which they were not an admin. This made it difficult for users to navigate between organizations in AMP. The "Organizations" menu will now be displayed to all users all the time, and it will only display organizations in which the user has a role OR in which there is at least one project and/or report to which the user has some level of access. When a user selects an organization, the Projects and Reports menus will be updated to show projects and reports that belong to the selected organization. The user will also be directed to the highest level dashboard to which they have access within the organization -- either the organization, project or report dashboard. |
| US1631 | Best Practices User Interface & Experience |
A "Standards" filter has been added to the redesigned Best Practices library in AMP. Users can now filter Best Practices to those that are mapped to a selected standard. |
| US1639 | Automated Testing Logs User Interface & Experience | When a spider encountered issues with a page that prevented it from being tested, the error message displayed on the spider errors page did not correctly indicate why the spider was unable to test the page. The error message has been improved to more clearly identify the cause of the error in these cases. |
| US1605 | Manual Testing | When adding a module manually users could not specify the browser. Furthermore, when adding modules to a report via the Firefox toolbar, "Firefox" was automatically selected as the browser for testing, even if the Firefox toolbar was only being used to add modules to the report. This sometimes resulted in reports that inaccurately reported the browsers in which the testing was done. Users can now select the browser in which testing will be done when adding a module manually, and they can also edit the browser if the module is added via one of the toolbars. The browser options that can be selected have been expanded to include Internet Explorer, which is frequently used for testing. Note that testers cannot select Internet Explorer as the browser to emulate in automated tests. This enhancement is strictly for accurate reporting of browsers used in manual testing, for now. |
| US1688 | Best Practices User Interface & Experience | A new "Reset" option has been added to the Best Practices filters to allow users to quickly and easily reset all filter selections to the defaults. |
| DE1310 | Best Practices Organization Testing Control User Interface & Experience |
The updated Best Practices library in AMP was displaying Best Practices that were not enabled in the Organization Testing Control. This issue was fixed and patched on production. |
| DE1243 | Alchemy Accessibility Tests |
Alchemy was incorrectly including HREF elements in the test and fix for the "Avoid the sole use of device-dependent event handlers" Best Practice. These elements are no longer flagged in Alchemy. |
| DE1213 | AMP Toolbars Performance & Scalability Reports | Users were sometimes getting an error when attempting to add a module via the AMP Toolbar for Firefox. This appeared to be happening when the modules were being added to very large reports. Additional hardware has been added to the AMP configuration to better handle the load in these scenarios. |
| DE1327 | AMP Toolbars Browser Compatibility |
The AMP toolbar for Firefox was not working with the latest Firefox upgrade -- version 45. The toolbar was updated, signed by Mozilla and released to production. If you upgrade to Firefox 45 and your AMP toolbar is not working, please download the latest version of the toolbar from AMP and update. |
AMP 2016.2.0 Release Notes
| SSB ID | Component(s) | Detailed Release Note |
|---|---|---|
| US1615 | Reports | AMP users were previously permitted to merge reports on violations for different technology platforms, resulting in a broken report. Users will now be prevented from merging reports if their technology platforms differ. When merging reports, only reports with the same technology platform as the initially selected report will be available for selection. |
| US1592 | Spiders | AMP currently only allows two spiders to be run concurrently. For clients hosted on SSB's shared servers, this means that their spiders may be queued behind other clients who are also running spiders at the same time. To alleviate the wait time, additional servers have been added to the hosted AMP configuration to handle the clients with the most spider activity. This intended to be a short-term solution. In the next release, a longer-term solution will be introduced. Specifically, software changes will be introduced to allow many more spiders to run at once. |
| US1583 | Best Practices & Standards | The Standards tab in AMP has been redesigned to improve the user experience and user interface. Users can now more easily navigate Standards and their relevant child standards and Best Practices, but they can search for specific Standards and filter the list more easily. |
| US1556 | AMP Desktop | As indicated in the announcement for the last release -- AMP Release 2016.1.0 -- AMP Desktop has been sunsetted with this release. The tool will no longer be accessible for download or use, and it will no longer be supported via SSB Product Support. |
| US1572 | Modules | When creating or editing a module, users can now enter a longer string in the Module Path text field, which has been modified to accept larger text strings. |
| US1582 | Alchemy | The Automatic testing tree in Alchemy now has a Media Type filter, allowing users to filter Best Practices and their violations by media type (e.g., Forms). |
| US1602 | SSB University | University users who do not also have AMP licenses will now be able to login to University directly. |
| US1573 | Alchemy | The Alchemy extension for Internet Explorer can now be installed on Internet Explorer 11, in addition to the previously-supported Internet Explorer 10. |
| US1176 | User Experience | Standard users in AMP did not see the Organization menu on their personal dashboard, making it difficult for standard users to navigate across organizations that contained projects and/or reports to which the users had access to. This behavior has been changed so standard users who have access to projects and/or reports in more than one organization will now see the Organization menu on their personal dashboard. When a user selects an Organization, they will remain on their personal dashboard (since standard users do not have access to Organization dashboards), but their context will change so they can more easily select projects and reports in the selected organization. If a user is a standard user in one organization and an administration in another, the user will be directed to to the organization dashboard for the organizations to which they have admin permissions when those organizations are selected. |
| US1513 | Alchemy | The Alchemy extension for Chrome was refactored to allow the extension to be signed by Google. The extension is now signed and is available for download and installation with no additional configurations (such as installing in Developer mode). |
| US1561 | User Experience | When sorting or paginating data tables within AMP, a spinner was not appearing to indicate to the user that the action was taking place, in cases where the action was not completed instantaneously. |
| DE1213 | AMP Toolbar for Firefox | Users were sometimes getting an error when attempting to add a module via the AMP Toolbar for Firefox. This appeared to be happening when the modules were being added to very large reports. Additional hardware has been added to the AMP configuration to better handle the load in these scenarios. |
| DE1178 | Reports | In the Violation Instances report, the contents of the "Status" column were hidden when the user sorted the data by that column. |
| DE1148 | Reports | The Violation Instances report contained an unexpected "Edit" option. This has been removed. |
| DE1123 | Alchemy | In the Alchemy testing pane, when a user navigates to a webpage that was previously tested the last report the user saved to should be selected by default. This was not occurring as expected and has been corrected. |
| DE1155 | Alchemy | When saving to an AMP report from the Alchemy testing pane, the incorrect time was being shown in the message in the testing pane that indicated the report and the date and time the report was saved. |
| DE1162 | Permissions | When users clicked the button to edit project permissions, the edit window would not open. |
| DE1121 | Administration | System administrator users who were also members of multiple organizations were able to accidentally delete their primary organization in AMP, causing them to lose access to the application. Users will now no longer see the option to delete their primary organization. In order to delete it, they will need to select another organization as their primary and then delete the formerly primary organization. |
View the latest What's New article for more information on exciting new features.
Comments