When should code audits be concluded?
When should code audits be concluded?
Code audits should be concluded before the launch of a feature or releasing the software after all code for a feature is complete. This ensures that all potential issues and bugs are identified and corrected before the software is made available to users, ensuring a high-quality release. Conducting audits at this stage helps in catching any overlooked defects and ensures that the final product is robust and reliable.
The correct answer id D. When to Conduct Code Audits: Before Launch: Audits should be concluded before launching a feature or releasing the software. Throughout Development: Regular audits during development catch issues early.
should it be 'B'? Isn't it too late when you do an audit at "d" stage?
Code audits are also known as SAST and should be done after a feature is completed, so the code can be reviewed and then you run a DAST (dynamic auditing on the compiled code) before completing the development
which one is correct ?
A is the answer
Checking-in code means to upload code to main branch repository so that its administrator can review the code and finally update the project version