In further embodiments, one or more testing modules 302 may maintain a log or other testing data structure, with entries and/or records for a plurality of events (e.g., errors, failures, executing an operation, providing simulated and/or automated user input, satisfying a time period or timer, or the like). A testing module 302, in certain embodiments, may include testing data and/or references to testing data in the log or other testing data structure (e.g., screenshots, memory dump, variable values, pointer values, or the like). For example, a testing module 302 may automatically gather testing data (e.g., take a screenshot, save a memory dump, or the like) in response to an error, a failure, providing a simulated user input event, and/or another trigger. In one embodiment, a user may define what testing data is stored in a log or other testing data structure using a GUI of a testing module 302, or the like. A testing module 302 may store a log or other testing data structure on a device 102 and/or may stream or forward a log or other testing data structure to a testing module 302 on a different device 102. A testing module 302 may display one or more logs to a user in a GUI on an electronic display of a hardware device 102, remotely on a webpage served from a hardware device 102 over a data network 106, or the like.