The data for testing

  As you know,for function testing,we always really depend on data.Having effiency data,make testing more easily and quickly,we can focus on function point to test if it has no question.Especially for some complicated system.

  As you know,for a system,we always have two version code.One is branch,the other is head.Certainly,we often use different develop methods for different system.But,basically,this is normal.And we always develop new function on head,and deploy coding on branch before release in order to execute regression testing.So,at least,we need two server and two different set of database for testing.Maybe,one database is more clearly and easily for testing,as lots of data maybe ready to use.The other is more dirty,that is more convenience for discover issue in system.For clean one,always use before release.In that case,we don't need run a long and involute workflow to gain a fit data to test that point.However,as system,run workflow for several times is necessary and important,especially for big release.But I think if running workflow for every bug or spec,in a way,that is wasting time and resource.We will lose most of our energy on workflow,and maybe in that case we will tried for discover issue.Because we will familiar with those pages,additional,for test the point,we may run foregoing step quickly to see the result.These always make us missing trivial or major,even critical question.That is not very good,I think,can say that,this is always bad for our system and project.

  In essence,I think,this question is on data.One aspect,we should prepare enough data to test.We always front test serveral times for one point,as maybe operation wrong or mistake,or even system error.So if we have enough data to test,that will save lots of time to test other point.I think this is also a good way to improve our effiency.For the other view,in my mind,if we can prepare same data on different server,in this way,when we test any server we can use them.That will also put aside most of time to know requirement,write spec or something like that.I believe that also can make our project or testing work enter a good circle.

  As I just discover this question on my aspect,I don't know if this is reasonable and feasible.So if anyone have any thinking,please leave your comment,even reserve view.I'll thinking your point and modify this article if that is really reasonable.Thank for your reading and have a nice coming week.