Answer posted by Radhika on 2005-05-24 08:29:43: Verification takes place before validation, and not vice versa. Verification evaluates documents, plans, code, requirements and specifications. Validation
Latest Answer : thnx Radhika u hv really been helpful. ...
Answer posted by Radhika on 2005-05-23 18:10:57: Black Box Testing: Testing input/output without knowledge and/or regard of the internal code. Commonly designed/executed by test team. White
Latest Answer : testing tech....which we use to make testing easily like...equivalence partitioning,boundary value analysis etcMethodoly:The method we follow like v-model,waterfall,spiral etc ...
Answer posted by Radhika on 2005-05-23 18:12:32: Software configuration management (SCM) is the control, and the recording that are made to the software and documentation throughout the software development
Latest Answer : Managemet which configures the software is called SCM. here configuration means arrangement of the parts of the software.. software configuration management is the decipline for systematically controlling the changes that take place during ...
Latest Answer : when the test results do not contradict with test requirements or the system requriements.......and.............when there are no bugs found in the application. ...
Latest Answer : sorry krishI 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 ...
Latest Answer : I will share my exp of code analyzer. I have used coverity for code analysis. Coverity is a static code analysis tools. You run coverity on your piece of code to find bugs like un-initialized variables, un-initialized pointers, memory leaks to some extent, ...
Latest Answer : As per my knowledge,Its ur developer who is gonna test ur code.Basically testing of code and other stuff related to code comes under development part, while developing the application itself an developer is supposed to look after the functionality and ...
Latest Answer : a code which is 1.bug free 2.reusable 3.independent 4.less complexity 5.well documented 6. easy to chage is called good code ...
In an application currently in production, one module of code is being modified. Is it necessary to re- test the whole application or is it enough to just test functionality associated with that module?