Abstract: Disclosed are various embodiments for automatically testing and verifying applications. A user input profile is generated for an application by performing a static analysis on the application. Simulated user input for the application is generated based at least in part on the user input profile. Execution of the application is initiated in a computing device. The simulated user input is provided to the application executed in the computing device. It is verified whether the application meets performance criteria in the computing device.

Abstract: Disclosed are various embodiments for an error troubleshooting application. Error data is obtained from a client device. A correlated knowledge base is referenced to determine if a solution is associated with the error data. If a solution is associated with the error data, a notification embodying the solution is communicated to the client device. If a solution is not associated with the error data, a notification indicating the solution is unknown is communicated to the client device.

Abstract: Disclosed are various embodiments for a state monitoring application. A state monitoring application initiates the execution of test operations on a client device. States of the client device are monitored to determine when the client device is at risk of entering an unresponsive state. When the client device is at risk, the state monitoring application initiates the execution of remedy operations to prevent the client device from becoming unresponsive.

Abstract: Disclosed are various embodiments for an error troubleshooting application. Error data is obtained from a client device. A correlated knowledge base is referenced to determine if a solution is associated with the error data. If a solution is associated with the error data, a notification embodying the solution is communicated to the client device. If a solution is not associated with the error data, a notification indicating the solution is unknown is communicated to the client device.

Abstract: Disclosed are various embodiments for defining tasks to be assigned to a service provider. In one embodiment, a specification of a service provider availability of a service provider from a client device is facilitated over a publically accessible network. At least one of a plurality of tasks are identified that are compatible with the service provider availability. One of a plurality of fulfillment alternatives is automatically selected for each identified at least one of the tasks. The identified at least one of the tasks is assigned to the service provider for fulfillment.

Abstract: Disclosed are various embodiments for automatically testing and verifying mobile applications. A mobile application is obtained from a source entity. The mobile application is automatically installed in different mobile computing devices in a testing environment. Execution of the mobile application is automatically initiated in the different mobile computing devices. Whether the mobile application meets performance criteria is automatically verified for each of the different mobile computing devices.

Abstract: Disclosed are various embodiments for an error troubleshooting application. Error data is obtained from a client device. A correlated knowledge base is referenced to determine if a solution is associated with the error data. If a solution is associated with the error data, a notification embodying the solution is communicated to the client device. If a solution is not associated with the error data, a notification indicating the solution is unknown is communicated to the client device.

Abstract: Disclosed are various embodiments for automatically testing and verifying mobile applications. A mobile application is obtained from a source entity. The mobile application is automatically installed in different mobile computing devices in a testing environment. Execution of the mobile application is automatically initiated in the different mobile computing devices. Whether the mobile application meets performance criteria is automatically verified for each of the different mobile computing devices.

Abstract: Disclosed are various embodiments for identifying user interface improvements from observed user behavior. A use case description is obtained from a developer of an application. Usability metrics are collected that observe interaction of a plurality of users with a user interface of the application. The usability metrics are analyzed in conjunction with the use case description to identify at least one aspect of the user interface for improvement. The aspect includes a page or an actionable element. Information is provided to the developer about the at least one aspect of the user interface identified for improvement.

Abstract: Disclosed are various embodiments for the contextual indexing of applications using an application analyzer. In one embodiment, the application analyzer identifies at least one used element present in an application. The application analyzer computes a weight for the at least one used element, then provides the at least one used element and the respective weight to a contextual index service.

Abstract: An application monitoring system determines the health of one or more resources used to process a transaction, business application, or other computer process. Performance data is generated in response to monitoring application execution and processed to determine and an actual and baseline value for resource usage data. Resource usage baseline data may be determined from previous resource usage data associated with a resource and particular transaction (a resource-transaction pair). The baseline values are compared to actual values to determine a deviation for the actual value. Deviation information for the time series data can be reported through an interface or some other manner.

Abstract: Application health is determined by calculating baseline deviation for one or more transactions based on past data having the same context as current data being examined. The performance data is generated in response to monitoring one or more applications that perform transactions during a time period. The performance data may include transaction metric data and the context data describing conditions under which one or more transactions were performed. A baseline is determined by predicting current or recent transaction performance data values using past transaction performance data associated with the same context. Based on the comparison of the actual and predicted data with the same or similar context, a deviation from the baseline value is determined for the transaction and reported, for example to a user through an interface.

Abstract: Application data is reported in response to monitoring an application transaction. Application data is obtained for an initial period of time. A function which estimates the application data is then identified for the reported application data. After identifying the function, subsequent application data is obtained, and function data is generated from the subsequent application data. The function data may be associated with function parameters associated with the identified function. A function can then be constructed from the reported function data. The function constructed from the function data may estimate application data associated with the monitored transactions.

Abstract: Application health is determined by calculating baseline deviation for one or more transactions based on past data having the same context as current data being examined. The performance data is generated in response to monitoring one or more applications that perform transactions during a time period. The performance data may include transaction metric data and the context data describing conditions under which one or more transactions were performed. A baseline is determined by predicting current or recent transaction performance data values using past transaction performance data associated with the same context. Based on the comparison of the actual and predicted data with the same or similar context, a deviation from the baseline value is determined for the transaction and reported, for example to a user through an interface.

Abstract: An application monitoring system determines the health of one or more resources used to process a transaction, business application, or other computer process. Performance data is generated in response to monitoring application execution and processed to determine and an actual and baseline value for resource usage data. Resource usage baseline data may be determined from previous resource usage data associated with a resource and particular transaction (a resource-transaction pair). The baseline values are compared to actual values to determine a deviation for the actual value. Deviation information for the time series data can be reported through an interface or some other manner.

Abstract: Application data is reported in response to monitoring an application transaction. Application data is obtained for an initial period of time. A function which estimates the application data is then identified for the reported application data. After identifying the function, subsequent application data is obtained, and function data is generated from the subsequent application data. The function data may be associated with function parameters associated with the identified function. A function can then be constructed from the reported function data. The function constructed from the function data may estimate application data associated with the monitored transactions.