Abstract: Techniques are disclosed herein for reactively identifying software products, available from an electronic marketplace, that are exhibiting anomalous behavior. Data associated with software products is accessed and analyzed to determine anomalous behavior. The data analyzed may include, but is not limited to, crash data, ratings data, marketplace data, usage data, and the like. A machine learning mechanism may be used to classify the application into a category relating to whether a potential anomaly is identified for the software product. A score may also be calculated for the software applications that indicates a severity of the anomalous behavior. The classification and/or the score may be used to determine whether to perform further analysis or testing with regard to a software product. For instance, the score may be used to determine that the software product is to be tested by a testing service.

Abstract: Techniques are disclosed herein for identifying software products, available from an electronic marketplace, to be tested. Data associated with software products is accessed and analyzed to determine what software products to test. The data analyzed may include, but is not limited to, download data, crash data, ratings data, marketplace data, usage data, and the like. A machine learning mechanism may be used to predict a popularity of a software product, classify the application into a category relating to whether a potential anomaly is identified for the software product, and determine whether to test the software product. A score may also be calculated for the software products that indicates whether or not to test the software product. The predicted popularity, the classification and/or the score may be used to determine whether to perform further analysis or testing with regard to a software product.

Abstract: A workflow processing system may receive a representation of one or more objects corresponding to the current state of a workflow. A rule may be mapped to one or more activities of the workflow. The rule may comprise an any-of clause, an all-of clause, and a none-of clause. Each clause may contain zero or more conditions that are evaluated with respect to the current state of the workflow. When each of the any-of, all-of, and none-of clauses evaluates to true, the rule may be satisfied and the activities to which the rule is mapped are performed.