Escuela Profesional de

Ingenieria de Sistemas
UCSM

Mgter. Carlo Corrales Delgado

ccorrales@ucsm.edu.pe

Testing, implantación y
mantenimiento de Sistemas
98-379: OBJECTIVE 3
Create Software Tests
LESSON 3.4
Describe Feature Tests
OVERVIEW Lesson 3.4

In this lesson, you will review the following:

• Distinguishing the functionality in the appropriate feature test.
GUIDING QUESTIONS Lesson 3.4

• What is a feature test?

• Who should be the focus of a usability test?
• What name is used to describe an automated test of the user
interface?
LECTURE Lesson 3.4

Software features
• A feature, from a development perspective, is a capability available
to the user.
• The features of a project are determined largely by the user stories
created during the initial planning process.
» Often, each independent user story is a description of a feature in the
final product. If a user story states that a customer should be able to pay
for an order with a credit card, then accepting credit card payments
becomes a feature of the product.
• Features may share overlapping functionality in the code. For
example, the same project may also accept other forms of payment.
• Likewise, some features may be accessible in different ways. Think
about the different ways the user can underline text in Microsoft
Word, for example.
LECTURE Lesson 3.4

Feature testing
• While well-designed unit and integration tests may provide excellent
code coverage and help ensure the units work meet the internal
specifications of the developers, it is important that the functionality
of each feature is tested.
• Each feature in an application should be tested independently.
• A test that focuses on the functionality of an individual feature in the
software, independent of other features, is called a feature test.
• In many cases, black box testing is used to testing functionality.
• The big-picture goal of feature testing is to ensure the features
implemented in the software meet or fit the user requirements.
LECTURE Lesson 3.4

Exploratory testing
• Sometimes called ad hoc testing, exploratory testing encourages the
tester to use the features of the software in a variety of ways.
• Often, effective exploratory testers use software in ways the
development team might not have anticipated. This can reveal
unexpected bugs.
• Despite the name, quality exploratory tests are more than just
running a program and trying things out—the tester should have a
plan and specific testing criteria. If those criteria are not met, the test
fails.
LECTURE Lesson 3.4

Usability testing
• Usability testing involves the study of how end-users interact with
the software.
• This provides valuable feedback related to ease-of-use and customer
satisfaction.
• Although usability tests are not necessarily a part of feature testing,
examining how users operate a specific feature can give insight into
potential flaws.
• By definition, usability tests by end-users are black box tests.
LECTURE Lesson 3.4

User Interface (UI) testing

• Any test of the operation and functionality of the user interface itself
is considered a UI test.
• Since the user interface is usually integral to the implementation of a
feature, UI testing is critical.
• Automated tests of the user interface are referred to as coded UI
tests.
• Visual Studio allows the developer to create a coded UI test by
recording actions while the application is running.
IN-CLASS ACTIVITY Lesson 3.4

Scenario:
Litware, Inc. is developing a web application that will enable users to
organize and manage recreational basketball leagues. Jay Henningsen is
the project manager and he has guided the development team through
a couple of development iterations. The software meets Jay’s testing
objectives, but when he showed screenshots of the application to a
friend who is involved in a basketball league but not a technical
professional, he realized that non-technical users may have difficulties
using the system. It is apparent that his team needs to refresh its
understanding of user interface testing.
Directions:
• Create a simple application and implement a coded UI test by following
the directions at Walkthrough: Creating, Editing and Maintaining a
Coded UI Test http://msdn.microsoft.com/en-us/library/ff977233.aspx
IN-CLASS ACTIVITY Lesson 3.4

Follow up:
After completing the walkthrough activity, share your experiences with
a partner.

• What difficulties did you experience?

• How did you resolve them?
• Identify three things you learned from this activity.
REVIEW Lesson 3.4

Can you answer these?

• What is a feature test?
• Who should be the focus of a usability test?
• What name is used to describe an automated test of the user
interface?
ADDITIONAL RESOURCES
MSDN® Resources
Exploratory Software Testing
System Testing with Coded UI
Tests
Testing Concepts and Phases
Lesson 3.4
http://msdn.microsoft.com/en-
us/library/jj620911.aspx
http://msdn.microsoft.com/en-
us/library/jj620891.aspx
http://msdn.microsoft.com/en-
us/library/ff798502.aspx