For example, in certain embodiments, a testing module 302 on a device 102 may provide an administrator or a different system (e.g., a testing module 302 on a server 108) with a screenshot from the device 102 and/or an associated application, with a data structure (e.g., a file, a database, a database table, a database record, a log or log entry, a value for a variable, a value for a pointer, or the like) from the device 102 and/or an associated application, with a communication (e.g., one or more data packets, a payload, an API request, a query, or other input/output (I/O) data to or from the device 102 and/or an associated application), with one or more identifiers of and/or execution data for one or more executing processes (e.g., data from volatile memory, data from a file system, data from a run-time stack, or the like), with an identifier of a device 102 (e.g., a make, a model, a manufacturer, a vendor, a version number, a name, or the like), with an identifier of an application executing on a device 102 (e.g., an application name, an application version number, an operating system version, or the like) and/or other data.