Methods for testing a very large application
I have a PHP app which is very large. There are usually 2-3 developers working on it full time and we are getting to the point where we are making changes and creating bugs (cough features!). The software isn’t complex per say, just there is a lot going on (35~ controllers, about the same models, etc).
Unit Tests code duplication?
How can I avoid code duplication in unit tests?
Why it is necessary to to test my iPhone app on actual iPhone device
I developed one application for iPhone and now I want it on App Store. So many my iOS geek friends told me to test it on actual device i.e. on iPhone.
How to test a random-generating feature in application? [duplicate]
Possible Duplicate:
How should I test randomness?
What Are Some Tips For Writing A Large Number of Unit Tests? [closed]
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for […]
Data Quality in Relational Database Regression Tests
I have been working on an open source Museum Collections Management web application that is to be used to keep track of a museum’s accessioned, donated, loaned or otherwise acquired artefacts.
Must all new features go through betatest?
Obviously, small usability fixes and bugfixes go directly into the stable product. What about small new features? Can you afford to just release them after internal testing, or do they have to be betatested by customers first?
ISTQB terminology question (Defect)
According to ISTQB (and few more sources + wiki ), a defect/bug is the actual cause of error in software, e.g. incorrect statement, logical or semantic error. The actual definion is: a flaw in the system or component that could lead to the failure.
But what about specification bugs? I cannot relate to it. Specification bugs are quite common but if the programmer implements software according to spec with a bug, it is not his fault (IMHO). But then the definion could not apply and I am sure it must have been addressed somehow. Could you help me to understand this?
Bug severity classification issues
In a book I have, there is a following classification of defect:
Where (if there is) is the IEEE glossary newer than 1990?
I have been looking for some formal definitons but could not find any IEEE newer than 610, which is from 1990. Could you help me please?