How to start automatic testing of a large application?

EDIT: thanks to ncie commentators, I get the difference between module and automatic testing, so I renamed the topic

Environement: .net 2.0, sql server 2005, Windows Server 2003

I read this article:

http://www.codeproject.com/KB/tips/convince.aspx

This guy talks about how you can add automated testing to an existing application without changing everything.

And I have to say that this article is really awesome, and make me try!

So, our system is almost the same: all data is accessible through web services, so we can easily (for example, using soapui) automatically test these web services.

BUT: what about the database? In order to conduct automatic testing, we need to have the correct data in the database corresponding to the automatic test.

For example, if I want to do an automatic test verifying that the software is causing an error, if the client name is empty, I need to add a client with an empty name in my db.

here is how i think i can do this:

  • create a server with everything he needs (iis, sql server ...)
  • add something so that the date of this server never changes, so I don’t need to change the time in my automatic test
  • add the records that I need to my database to perform my automatic test.

: 10 , , . , "TEST_NAME" , .

- ​​? ? ? (, , ).

EDIT: 2 -1 , , .

+3
3

- , - . , unit test, , , . -. , , .

, , , :

interface IRepository
{
   GetModel(id);
   SaveModel(model);
}

unit test to / . , , , .

+1

, , , .

0

If you can generate your test data before each batch of tests, then your records start with an identifier equal to the next number equal to 100. Therefore, if the largest record is 350, generate a run of 400 and a test with 400 and higher, When your database becomes really big, delete everything.

0
source

Source: https://habr.com/ru/post/1784767/


All Articles