The Gurus Guide to SQL Server Stored Procedures, XML, and HTML [Electronic resources] نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

The Gurus Guide to SQL Server Stored Procedures, XML, and HTML [Electronic resources] - نسخه متنی

Ken Henderson

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
لیست موضوعات
توضیحات
افزودن یادداشت جدید









Types of Tests



There are several different types of tests. In my work, four have proved to be the most valuable: unit tests, functional tests, regression tests, and integration tests. Let's discuss each type separately.


Unit Tests



Unit tests are written by programmers to ensure that programs work as they're supposed to. What defines what a program is supposed to do? The specifications and design laid out earlier. Unit tests are often built right into the software, with conditional defines either including or excluding them from the compiled executable. Unit tests affirm, module by module, that code correctly implements the functionality the programmer thinks it's supposed to have. Unit tests help identify software bugs.


Functional Tests



Functional tests are specified by users to ensure that the system as a whole works the way they think it should. Functional tests are more holistic and all encompassing. They are also more final than unit tests. A system can be devoid of bugs and still not pass functional tests. The final word on whether a system performs as it's supposed to rests with its users.


Regression Tests



Regression tests are tests that compare the results from multiple test runs with one another, usually using automated tools. A regression test ensures that the results from tests today match those from yesterday.


Integration Tests



Integration tests ensure that the various modules that make up a system play well together. They ensure that changes made in one unit don't break code in another at a distance. Because the XP methodology encourages early and constant integration, the entire development process is itself a type of integration test. Other methodologies relegate integration testing to regular intervals during the development process (say, weekly or monthly, for example), but are careful to isolate problematic modules so that they do not produce bad buildsin other words, builds that cannot be used or tested meaningfully because of fatal flaws in a specific module.



/ 223