RE: How do you know your code has met specifications when there are no specifications?
Withour requirements one cannot validate the software whether it has met the requirements or not. In this case the customer's acceptance can be treated as meeting the specifications.
RE: How do you know your code has met specifications w...
By doing the ad-hoc testing one can know the application has met the specifications or not. ad-hoc testing is a testing when a tester tries to break the system by randomly trying the system's functionality.
RE: How do you know your code has met specifications w...
sorry krish
I have another opinion same as above to agree with as UAT is where the client will sign off on each stage as different modules are being incorporated within the application.
as long as the customers happy your happy at each stage.
client is always notified of the importance of specifications and if not then your in a problem because then the client will expect a perfect apple with no bruises.
