what is code validation?

Question

Is code validation done after code review or is it done after unit/integration testing?

Answer 1

I don't think there's a single accepted definition of exactly what "code validation" is. It most commonly refers to a process (often automated) of ensuring that code meets specific formal requirements, that is, that it is "valid".



As for when it's done, most software processes are circular, not linear. So any process done after code review X is also done before code review X+1. Generally, every acceptance process is done any time one is considering accepting the code, and validation is usually an acceptance process.



If units have specific validation requirements, they should be checked before unit integration. Sometimes some units will have specific validation requirements. For example, can an XML parser parse all standard XML test documents? Does it generate errors on all reference errored documents? Such a test would generally be done prior to integration or combined testing. (Why waste time integrating and testing integration of a buggy parser?)

Answer 2

Code validation is checks added to the code to make sure that:

1. users/surfers do not hack into your code and cause problems.

2. users/surfers make required entries into a form.

3. your code will not break.



It can be created using programming on the server side or the client side (javascript)



When you fill in a form and submit it and you get a pop up that says "error: you must do ???? or fill in this field.....that is validation.



It is good to do validation before testing because 9 time out of ten if you don't the testers will point out instances where validation was needed and you didn't validate. (ie. the form says enter your age and it lets me enter letters)

Answer 3

is use of numbers