Systems and methods for automated code validation
Systems and methods in accordance with embodiments of the invention can automatically track the creation of documents, such as source code files and unit tests, along with the development of those documents. The document creation and development workflow can be automatically validated against a defined set of standards to ensure that the documents are properly created. The review of the documents can also be automatically validated to ensure that the review process is properly completed. A variety of metrics can be generated regarding errors and issues identified during the validation processes. These metrics can be used to identify common issues, automatically generate proactive suggestions to avoid issues during document creation and testing, and/or generate developer profiles indicating the performance of particular developers.
1. A method, comprising:
generating, by a computing device, a document based on document requirement data;
identifying, by the computing device, a set of unit tests based on the document requirement data and corresponding to the document;
predicting, via a machine learning model and based on a machine learning classifier trained on at least a dataset of common errors, in real-time an error within the document without compiling the document;
generating, via the machine learning model, a correction recommendation to correct the error;
predicting, without compiling or testing the document, a break build likelihood indicative that the correction recommendation to the document would break a build process by causing a stored associated document in version control to fail to compile post commit;
receiving a revision of the document based on the correction recommendation and the break build likelihood of the correction recommendation;
calculating, by the computing device, a code coverage metric based on the set of unit tests based on the document requirement data performed on the document and passed;
calculating, by the computing device, one or more quality metrics based on zero or more linter errors in the document; and
when the code coverage metric exceeds a coverage threshold value and the one or more quality metrics exceeds a quality threshold value, transmitting, by the computing device and to a version control system, a check-in request comprising the document and the set of unit tests.
2. The method of claim 1 , wherein:
the document requirement data comprises an indication of a first creation date of the document and an indication of a second creation date of the set of unit tests; and
validating the document further comprises determining that the second creation date is prior to the first creation date.
3. The method of claim 1 , wherein the method further comprises determining an amount of time spent refactoring the document.
4. The method of claim 1 , wherein the method further comprises determining a number of refactors of the document.
5. The method of claim 1 , further comprising:
determining, by the computing device, a set of coding errors as the zero or more linter errors in the document by linting the document; and
validating the document based on the set of coding errors.
6. The method of claim 1 , further comprising:
transmitting, by the computing device, validation results for the document;
obtaining, by the computing device, feedback determined based on the validation results; and
providing, by the computing device, the feedback.
7. The method of claim 6 , wherein the feedback is provided in real-time.
8. A computing device, comprising:
a processor; and
a memory in communication with the processor and storing instructions that, when executed by the processor, cause the computing device to:
generate a document based on document requirement data;
identify a set of unit tests based on the document requirement data and corresponding to the document;
predict, via a machine learning model and based on a machine learning classifier trained on at least a dataset of common errors, in real-time an error within the document without compiling the document;
generate, via the machine learning model, a correction recommendation to correct the error;
predict, without compiling or testing the document, a break build likelihood indicative that the correction recommendation to the document would break a build process by causing a stored associated document in version control to fail to compile post commit;
receive a revision of the document based on the correction recommendation and the break build likelihood of the correction recommendation;
calculate a code coverage metric based on the set of unit tests based on the document requirement data performed on the document and passed;
calculate one or more quality metrics based on zero or more linter errors in the document; and
when the code coverage metric exceeds a coverage threshold value and the one or more quality metrics exceeds a quality threshold value, transmit, to a version control system, a check-in request comprising the document and the set of unit tests.
9. The computing device of claim 8 , wherein:
the document requirement data comprises an indication of a first creation date of the document and an indication of a second creation date of the set of unit tests; and
the instructions, when executed by the processor, further cause the computing device to validate the document by determining that the second creation date is prior to the first creation date.
10. The computing device of claim 8 , wherein the instructions, when executed by the processor, further cause the computing device to validate the document by determining an amount of time spent refactoring the document.
11. The computing device of claim 8 , wherein the instructions, when executed by the processor, further cause the computing device to validate the document by determining a number of refactors of the document.
12. The computing device of claim 8 , wherein the instructions, when executed by the processor, further cause the computing device to:
determine, by the computing device, a set of coding errors as the zero or more linter errors in the document by linting the document; and
validate the document based on the set of coding errors.
13. The computing device of claim 8 , wherein the instructions, when executed by the processor, further cause the computing device to:
transmit validation results for the document;
obtain feedback determined based on the validation results; and
provide the feedback.
14. The computing device of claim 13 , wherein the feedback is provided in real-time.
15. A non-transitory machine-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform steps comprising:
generating a document based on document requirement data;
identifying a set of unit tests based on the document requirement data and corresponding to the document;
predicting, via a machine learning model and based on a machine learning classifier trained on at least a dataset of common errors, in real-time an error within the document without compiling the document;
generating, via the machine learning model, a correction recommendation to correct the error;
predicting, without compiling or testing the document, a break build likelihood indicative that the correction recommendation to the document would break a build process by causing a stored associated document in version control to fail to compile post commit;
receiving a revision of the document based on the correction recommendation and the break build likelihood of the correction recommendation;
calculating a code coverage metric based on the set of unit tests based on the document requirement data performed on the document and passed;
calculating one or more quality metrics based on zero or more linter errors in the document; and
when the code coverage metric exceeds a coverage threshold value and the one or more quality metrics exceeds a quality threshold value, transmitting, to a version control system, a check-in request comprising the document and the set of unit tests.
16. The non-transitory machine-readable medium of claim 15 , wherein:
the document requirement data comprises an indication of a first creation date of the document and an indication of a second creation date of the set of unit tests; and
validating the document further comprises determining that the second creation date is prior to the first creation date.
17. The non-transitory machine-readable medium of claim 15 , wherein the steps further comprises determining an amount of time spent refactoring the document.
18. The non-transitory machine-readable medium of claim 15 , wherein the steps further comprises determining a number of refactors of the document.
19. The non-transitory machine-readable medium of claim 15 , wherein the instructions, when executed by one or more processors, further cause the one or more processors to perform steps comprising:
determining a set of coding errors as the zero or more linter errors in the document by linting the document; and
validating the document based on the set of coding errors.
20. The non-transitory machine-readable medium of claim 15 , wherein the instructions, when executed by one or more processors, further cause the one or more processors to perform steps comprising:
transmitting validation results for the document;
obtaining feedback determined based on the validation results; and
providing, in real-time, the feedback.