Talk:Database testing
 | This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
| |||||||||||
Find sources
[edit]Overall low quality
[edit]First off, i support the initial part of the {{multiple issues}} "charge": this appears to have been created "essay-like"; though i've tried to change it a bit to solve this, there remain many paragraphs that aren't very "readable" IMO. Actually, even the WP:LEAD isn't doing its job properly.
The article also seems to go off-topic at times, and at occasion even make illogical claims:
- The Lead ends with having ACID for the DBMS, but that is not the database's concern.
- Having the three "outer" layers of UI, BL, and DAL is an issue for general Application testing, not specifically related to Database testing.
- "The UI layer deals with the interface design of the database"?!? No it doesn't, since a database has no interface, and should have no direct interaction with users.
- The business layer doesn't require a "database supporting business strategies" either.
- "Testing at these different layers is frequently used to maintain consistency of database systems, most commonly seen in the following examples:" -- the list that follows doesn't provide any support for this statement.
- "Google or Symantec, who are associated with data storage"? I associate them with a Search Engine, and Anti-Virus Software, respectively...
- "Some companies have different types of databases, and also different goals and missions. In order to achieve a level of functionality to meet said goals, they need to test their database system." and "Database testing mainly deals with finding errors in the databases so as to eliminate them. This will improve the quality of the database or web-based system." -- These are just bloat, don't provide specific info ("some companies"? And if not eliminate, why else?), and might only fit in the Lead, if at all. Also, how is a "web-based system" relevant to Database testing?
- "The current approach of testing may not be sufficient [...] A separate database testing team seems advisable." -- No support for what the "current approach" is, or for its failures, and ends with a business suggestion... What is this, Software Company Management 101?
- "database crashes" seems hardly a correct term. Technically, a DB *cannot* crash, only a DBMS can, though maybe the intended meaning was that a DB can become "invalid" (or "inconsistent")...
- "database refactoring" is quite out of place after a mention of broken SQL...
- IMO, File:Nisarg123.jpg fails to present any relevant or valuable info.
- Of the "Data load testing" points, only the 4th is okay-ish, since it explains what DLT actually is. The other three points are quite off-topic, requiring a source and a destination database(?!), and detailing actions of "workers" (working processes maybe?)...
- There's more, but i've spent way too much time on this already.
So, basically, the current state of the "article" is poor enough that it would greatly benefit from WP:Expert attention... Myself, i am just somewhat accustomed to the subject so i could point out simple issues (like the list above), but i don't have enough knowledge to actually write this article. -- Jokes Free4Me (talk) 18:59, 24 January 2013 (UTC)