Главная Случайная страница


Полезное:

Как сделать разговор полезным и приятным Как сделать объемную звезду своими руками Как сделать то, что делать не хочется? Как сделать погремушку Как сделать так чтобы женщины сами знакомились с вами Как сделать идею коммерческой Как сделать хорошую растяжку ног? Как сделать наш разум здоровым? Как сделать, чтобы люди обманывали меньше Вопрос 4. Как сделать так, чтобы вас уважали и ценили? Как сделать лучше себе и другим людям Как сделать свидание интересным?


Категории:

АрхитектураАстрономияБиологияГеографияГеологияИнформатикаИскусствоИсторияКулинарияКультураМаркетингМатематикаМедицинаМенеджментОхрана трудаПравоПроизводствоПсихологияРелигияСоциологияСпортТехникаФизикаФилософияХимияЭкологияЭкономикаЭлектроника






Testing





1. Testing All testing involves all five dimensions. A testing technique focuses your attention on one or a few dimensions, leaving the others open to your judgment. You can combine a technique that is focused on one dimension with techniques focused on the other dimensions to achieve the result you want. You might call the result of such a combination a new technique (some people do), but we think the process of thinking is more useful than adding another name to the ever-expanding list of inconsistently defined techniques in use in our field. Our classification scheme can help you make those combinations consciously and thoughtfully. 71208_Kaner_CH03I 11/21/01 4:26 PM Page 32 Chapter 3: Testing Techniques 33 Testing tasks are often assigned on one dimension, but you do the work in all five dimensions. For example, ■■ Someone might ask you to do function testing (thoroughly test every function). This tells you what to test. You still have to decide who does the testing, what types of bugs you’re looking for, how to test each function, and how to decide whether the program passed or failed. ■■ Someone might ask you to do extreme-value testing (test for error handling when you enter extreme values into a variable). This tells you what types of problems to look for. You still have to decide who will do the testing, which variables to test, how to test them, and how you’ll evaluate the results. ■■ Someone might ask you to do beta testing (have external representatives of your market test the software). This tells you who will test. You still have to decide what to tell them (and how much to tell them) about, what parts of the product to look at, and what problems they should look for (and what problems they should ignore). In some beta tests, you might also tell them specifically how to recognize certain types of problems, and you might ask them to perform specific tests in specific ways. In other beta tests, you might leave activities and evaluation up to them. Techniques don’t necessarily fit on only one dimension. Nor should they; all testing involves all five dimensions, and so we should expect the richer test techniques to span several. Here’s an example of what can be a multidimensional technique: If someone tells you to do “requirements-based testing,” she might be talking about any combination of three ideas: ■■ Coverage (Test everything listed in this requirements document.) ■■ Potential problems (Test for any way that this requirement might not be met.) ■■ Evaluation (Design your tests in a way that allows you to use the requirements specification to determine whether the program passed or failed the test.) Different testers mean different combinations of these ideas when they say, “requirements-based testing.” There is no one right interpretation of this phrase.1

 

Date: 2015-09-18; view: 413; Нарушение авторских прав; Помощь в написании работы --> СЮДА...



mydocx.ru - 2015-2024 year. (0.007 sec.) Все материалы представленные на сайте исключительно с целью ознакомления читателями и не преследуют коммерческих целей или нарушение авторских прав - Пожаловаться на публикацию