Abstract: In some examples, test relevancy prediction for code changes may include ascertaining files for a commit for a build, and for each test of a plurality of tests, determining a score based on a weight assigned to a file of the ascertained files. Test relevancy prediction for code changes may further include ordering each test of the plurality of tests according to the determined score, and identifying, based on the ordering of each test of the plurality of tests, tests from the plurality of tests for which the score exceeds a specified threshold. The identified tests may represent tests that are to be applied to the build.

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: A technique includes receiving a plurality of metrics for a plurality of tasks associated with developing an application, where each of the metrics is associated with one of the tasks and indicates a progress of the associated task. The technique includes receiving weights, where each weight is associated with one of the tasks and indicates a user assigned importance of the associated task. The technique includes displaying with the tool an indicator to allow regulation of task development, where the displaying includes causing the tool to prioritize the tasks for future development of the application based at least in part on the metrics and the weights.

Abstract: In some examples, test relevancy prediction for code changes may include ascertaining files for a commit for a build, and for each test of a plurality of tests, determining a score based on a weight assigned to a file of the ascertained files. Test relevancy prediction for code changes may further include ordering each test of the plurality of tests according to the determined score, and identifying, based on the ordering of each test of the plurality of tests, tests from the plurality of tests for which the score exceeds a specified threshold. The identified tests may represent tests that are to be applied to the build.

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 technique includes receiving a plurality of metrics for a plurality of tasks associated with developing an application, where each of the metrics is associated with one of the tasks and indicates a progress of the associated task. The technique includes receiving weights, where each weight is associated with one of the tasks and indicates a user assigned importance of the associated task. The technique includes displaying with the tool an indicator to allow regulation of task development, where the displaying includes causing the tool to prioritize the tasks for future development of the application based at least in part on the metrics and the weights.