Abstract: An example technique involves sending, from a user device associated with a particular user, a request for a confirmation message setting. The request may include an indication of an identity of the particular user. The example technique involves determining that an operation included in a predetermined set of operations has been cued. The example technique involves receiving a response comprising an indication of a confirmation message setting for the cued operation prior to performing the cued operation. The confirmation message setting may be based on data generated responsive to the sent request. The confirmation message setting for the cued operation may include an indication of whether or not to output a confirmation message. The example technique involves determining, based on the received response, whether to prompt the particular user via a user interface of the user device for a response to a confirmation message prior to performing the cued operation.

Abstract: According to an example, usage of a plurality of features of an application by users in each of a plurality of tenants may be accessed. Popularities of the plurality of features among the users in each of the plurality of tenants may be determined and a feature of the plurality of features to be promoted to the users in the first tenant may be identified based upon the determined popularities of the features. Additionally, a visual callout to the identified feature may be caused to be displayed to the users in the first tenant to promote the identified feature to the users in the first tenant.

Abstract: In some examples, a system includes a segment identification engine and a coverage determination engine. The segment identification engine may a code segment in application code for updating a code coverage threshold applicable to the code segment. The coverage determination engine may update the code coverage threshold for the code segment based on a usage frequency of the code segment and a change frequency of the code segment.

Abstract: In some examples, a system includes a segment identification engine and a coverage determination engine. The segment identification engine may a code segment in application code for updating a code coverage threshold applicable to the code segment. The coverage determination engine may update the code coverage threshold for the code segment based on a usage frequency of the code segment and a change frequency of the code segment.

Abstract: An example technique involves sending, from a user device associated with a particular user, a request for a confirmation message setting. The request may include an indication of an identity of the particular user. The example technique involves determining that an operation included in a predetermined set of operations has been cued. The example technique involves receiving a response comprising an indication of a confirmation message setting for the cued operation prior to performing the cued operation. The confirmation message setting may be based on data generated responsive to the sent request. The confirmation message setting for the cued operation may include an indication of whether or not to output a confirmation message. The example technique involves determining, based on the received response, whether to prompt the particular user via a user interface of the user device for a response to a confirmation message prior to performing the cued operation.

Abstract: According to an example, usage of a plurality of features of an application by users in each of a plurality of tenants may be accessed. Popularities of the plurality of features among the users in each of the plurality of tenants may be determined and a feature of the plurality of features to be promoted to the users in the first tenant may be identified based upon the determined popularities of the features. Additionally, a visual callout to the identified feature may be caused to be displayed to the users in the first tenant to promote the identified feature to the users in the first tenant.

Abstract: Examples disclosed herein relate to software development managements. Some of the examples enable identifying a set of rules related to a software development methodology. Each rule of the set of rules may be associated with a rule-specific score. Some of the examples further enable monitoring a software development process, and determining, during the monitoring, whether at least one rule of the set of rules is invoked by an action performed by a user. If determined that a particular rule of the set of rules is invoked, a software development management score may be dynamically adjusted based on the rule-specific score associated with the particular rule. Some of the examples further enable providing a recommended action to increase the software development management score.

Abstract: A test-centric model of an application is constructed. Each resource specified by each test governing an application is added to the test-centric model. The test or tests specifying an resource are linked to the resource within the test-centric model. A composition of the application is defined using the one or more tests, as the resources specified by the one or more tests, within the test-centric model of the application.

Abstract: Evaluating documentation coverage can include identifying, from a testing tool having exercised an application, interface elements of the application's user interface. The identified interface elements are filtered to identify documentable interface objects. For each identified documentable interface object, it is determined if documentation exists for that documentable interface object. A value, indicative of the determined existence or non-existence of documentation, is assigned to each documentable interface object. Documentation coverage data is reported for the application interface. The coverage data is reflective of the values assigned to the documentable interface objects.

Abstract: Evaluating documentation coverage can include identifying, from a testing tool having exercised an application, interface elements of the application's user interface. The identified interface elements are filtered to identify documentable interface objects. For each identified documentable interface object, it is determined if documentation exists for that documentable interface object. A value, indicative of the determined existence or non-existence of documentation, is assigned to each documentable interface object. Documentation coverage data is reported for the application interface. The coverage data is reflective of the values assigned to the documentable interface objects.

Abstract: A test-centric model of an application is constructed. Each resource specified by each test governing an application is added to the test-centric model. The test or tests specifying an resource are linked to the resource within the test-centric model. A composition of the application is defined using the one or more tests, as the resources specified by the one or more tests, within the test-centric model of the application.

Abstract: A test-centric model of an application is constructed. Each resource specified by each test governing an application is added to the test-centric model. The test or tests specifying an resource are linked to the resource within the test-centric model. A composition of the application is defined using the one or more tests, as the resources specified by the one or more tests, within the test-centric model of the application.

Abstract: Example embodiments relate to code routine performance prediction using test results from code integration tool. An example system may include a code integrator to merge multiple developer committed copies of code for an application and automatically run tests on the merged code. The code integrator may gather performance information of a pre-written code routine included in the merged code, where the performance information is generated in response to the tests. The system may include a code routine performance manager to receive and store the performance information of the pre-written code routine. The system may include a code development environment to allow a developer of the application to create and modify a working copy of code for the application. The code development environment may receive the performance information of the pre-written code routine when the pre-written code routine is included in the working copy of the code.

Abstract: Example embodiments relate to creating test templates based on steps in existing tests. In example embodiments, a testing computing device may select an existing test from multiple existing tests. Each existing test of the multiple existing tests may include a set of distinct steps. The testing computing device may determine a sub-sequence related to the selected existing test. The sub-sequence may be based on a subset of the distinct steps included in the selected existing test. The testing computing device may determine that the distinct steps in the subset occur in a number of existing tests from the multiple existing tests, and may generate a test template using the sub-sequence. The test template may include the distinct steps in the subset.

Abstract: A test-centric model of an application is constructed. Each resource specified by each test governing an application is added to the test-centric model. The test or tests specifying an resource are linked to the resource within the test-centric model. A composition of the application is defined using the one or more tests, as the resources specified by the one or more tests, within the test-centric model of the application.

Abstract: Example embodiments relate to creating test templates based on steps in existing tests. In example embodiments, a testing computing device may select an existing test from multiple existing tests. Each existing test of the multiple existing tests may include a set of distinct steps. The testing computing device may determine a sub-sequence related to the selected existing test. The sub-sequence may be based on a subset of the distinct steps included in the selected existing test. The testing computing device may determine that the distinct steps in the subset occur in a number of existing tests from the multiple existing tests, and may generate a test template using the sub-sequence. The test template may include the distinct steps in the subset.