What is good code?
Answers were Sorted based on User's Feedback
Answer / rad
These are some important qualities of good code
Cleanliness: Clean code is easy to read; this lets people
read it with minimum effort so that they can understand it
easily.
Consistency: Consistent code makes it easy for people to
understand how a program works; when reading consistent
code; one subconsciously forms a number of assumptions and
expectations about how the code works, so it is easier and
safer to make modifications to it.
Extensibility: General-purpose code is easier to reuse and
modify than very specific code with lots of hard coded
assumptions. When someone wants to add a new feature to a
program, it will obviously be easier to do so if the code
was designed to be extensible from the beginning.
Correctness: Finally, code that is designed to be correct
lets people spend less time worrying about bugs and more
time enhancing the features of a program.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / radhika
A code whether it is good or bad can be known only if it is
tested. So good coding ,results in low bug density(Low
severity +Low prioirity defects or no defects at all)
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / rajeshwar rao
A good code which is===1. Bug free.2.
reusable.3.independent.4.less complaxcity.5.well documented
easy to change is called good code
| Is This Answer Correct ? | 0 Yes | 0 No |
In the team both developers as well as testers will be included na,if so then the same TL will assign the work for testers also or else TL will be different for testers?
What is severity ?
What is the difference between Retesting and Data Driven Testing?
what is equivalence boundary
What is unit level testing?
Could anyone share FAQs for Test Manager position...
How do u write integration test cases?do u have any special format?
how is security testing done in ecommerece application?
diff b/w regression, re-testing & repeative testing
what is sign off process in manual testing?
1 Answers Cap Gemini, Virtusa,
there are 100 test cases. and u got a bug at 85th test cases. u reported it to dev and dev fixed that bug. when u r doing regression testing from whic test case u'll do tetsing?? will start from 85 th test case are u'll execute 100 test cases??
As soon as we get the build what type test we will do?and how?