Quote:
|
You're seeing this from a big company point of view....
|
Not at all. I have worked on everything from Mom and Pop operations to government contracts over the last ten years. The basic rules of good software development do not change, just the method of implementing them. How small is Bookeen?
Irrespective of the development team size using proper testing strategy and test scripts (including regression as has been mentioned in this thread) will still ensure bugs like this don't make it to production. This is a basic necessity of good software development and there is no excuse for not doing it. It's hardly complicated either, for each requirement you must have a test which you must perform and pass prior to a release.
e.g. (obviously would require more detail)
Requirement: The Library View displays the list of books on the device with Title, Author and Published Date retrieved from the ebooks meta data as per the epub spec.
Validation: Add an epub ebook to the device with known Title, Author and Published date. Open the Library View on the device and confirm the book is displayed with the known data.
A couple of minutes to write (once) and less than a minute to run.
If this test was not performed prior to release (or worse, not written) then someone was not doing their job properly. Not harsh. Not pretentious. Just a fact.
There is also Unit testing and Automated Testing which possibly could have caught this issue before release.