-
公开(公告)号:US11494288B2
公开(公告)日:2022-11-08
申请号:US15680092
申请日:2017-08-17
Applicant: EntIT Software LLC
Inventor: Gabi Shalev , Itay Ben-Yehuda , Raz Regev , Elad Benedict
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.
-
公开(公告)号:US10169223B2
公开(公告)日:2019-01-01
申请号:US15491542
申请日:2017-04-19
Applicant: EntIT Software LLC
Inventor: Ohad Assulin , Elad Benedict , Shaul Strachan , Raz Regev , Gabi Shalev
Abstract: Techniques for identifying a build commit that caused a test failure are provided. A build which includes a failed test may be identified. For each commit in the build a weighting factor may be calculated for files that have been previously associated with the failed test. The weighting factor may be based on the number of times the file has been associated with the failed test and the total number of tests. A weighting factor may also be calculated for files that have not been previously associated with the failed test based on the number of times the file appears with other files that are associated with the failed test. The weighting factors may be added to create a score for the commit. The scores for the commits in the build may be ordered. The higher the score, the more likely the commit was the cause of the failed test.
-
公开(公告)号:US20180307593A1
公开(公告)日:2018-10-25
申请号:US15491542
申请日:2017-04-19
Applicant: EntIT Software LLC
Inventor: Ohad Assulin , Elad Benedict , Shaul Strachan , Raz Regev , Gabi Shalev
CPC classification number: G06F11/3692 , G06F8/71
Abstract: Techniques for identifying a build commit that caused a test failure are provided. A build which includes a failed test may be identified. For each commit in the build a weighting factor may be calculated for files that have been previously associated with the failed test. The weighting factor may be based on the number of times the file has been associated with the failed test and the total number of tests. A weighting factor may also be calculated for files that have not been previously associated with the failed test based on the number of times the file appears with other files that are associated with the failed test. The weighting factors may be added to create a score for the commit. The scores for the commits in the build may be ordered. The higher the score, the more likely the commit was the cause of the failed test.
-
-