Talk:Migration testing

A member of the Guild of Copy Editors reviewed a version of this article for copy editing. However, a major copy edit was inappropriate at that time because of the issues specified below, or the other tags now found on this article. Once these issues have been addressed, and any related tags have been cleared, please tag the article once again for {{Copy edit}}. The Guild welcomes all editors with a good grasp of English. Visit our project page if you are interested in joining!

This page reads like it has been copied from a student textbook or lecture notes. Should it be kept as an article? NicoluxHC (talk) 22:01, 21 August 2013 (UTC)[reply]

No opinion on NicoluxHC's question above. The article does not say WHY "Database migration testing is needed when data is moved from one database(s) to another." or give any standards to which such testing would be designed. It also cites numerous types of tests without explanation or links as to their purpose or design. Very jargon riddled; wikipedia readers are a broader audience than experts or techs in a field. Perlucidus (talk) 18:48, 23 March 2014 (UTC)[reply]

This article has been largely pasted from Arsin's website, including the item "Run Arsin’s TSP’s/DBQGen utility to validate the data between source and target databases". — Preceding unsigned comment added by 122.56.23.164 (talk) 21:06, 8 June 2014 (UTC)[reply]

It hardly even describes what the heck migration testing is in the first place. It also needs description on the history of the term. Who coined it, or popularized it? -AngusWOOF (talk) 23:05, 18 September 2014 (UTC)[reply]