||Fixed: It was impossible to view or download files attached to test steps.
||Fixed: QAComplete could throw the
No form name passed error when creating a filter.
||Fixed: When importing test cases from a .csv file, only the first test case was imported successfully.
||Fixed: When updating notes of agile tasks, the Latest Note field of the Edit Agile Task form showed an empty string rather than the contents of the updated note.
||Fixed: The Steps field in reports showed no information on test steps.
||Fixed: The TestAgentSettings utility was able to access Test Agent settings without administrator privileges.
||Fixed: In Google Chrome, upon editing a title of a test and then moving to a subsequent test, the product could replace the title of the subsequent test with the title of the preceding test.
||Fixed: When editing test steps, the Test Runner could fail to save the changes made to the test step status and returned them to their initial In Queue state.
||Fixed: When running a test set, the Test Runner moved to a subsequent test only if all the test steps in the current test had passed, and failed to move to the subsequent tests if the current test contained skipped, failed, or blocked steps.
||Fixed: If a test contained failed and blocked test steps, the Test Runner determined the test status as blocked rather than failed, and did not show the Auto Create New Defect dialog for such tests.
||Fixed: The Test Runner did not show error messages for errors that occurred during test runs.
||Fixed: When updating the product, the psSQLUpdater utility could terminate the updating process if the QAComplete database was too large and SQL scripts were running for a long time.
||Fixed: The renewed license could not be applied to the QAComplete if the QAComplete database did not contain information on the user who originally activated the license.
||Fixed: QAComplete could not import data from .csv files if a temp directory did not exist in the FileExchange folder.
Features Added to QAComplete 11.2, October 2016