Information Technology Reference
In-Depth Information
• Searchability is a very difficult thing to test for, but it is a great asset to your web
site. If you would like to allow web crawlers to index your page there are a
couple tips to make this more efficient.
• If using Ajax, use comment tags to hold content that may be dynamically
inserted. This provides proper indexing.
• Do not use images for text. Image text is harder to index and most web crawlers
will not index the internal text of images. If you do use images for text use the
alt attribute to insert a brief and proper description.
• Do not try to get higher page ranks by placing what you believe to be highly
searched terms in the head tags.
10.9 Unit Testing
Unit testing is testing of the systems components, as components rather than a
system as a whole. First, unit testing reduces the complexity of overall test
activities, allowing us to focus on smaller units of the system. Second, unit testing
makes it easier to pinpoint and correct faults, given that few components are
involved in the test. Third, unit testing allows parallelism in the testing activities;
that is, each component can be tested independently of the others. The specific
candidates for unit testing are chosen from the object model and the system
decomposition. The minimal set of objects to be tested should be the participating
objects in use cases. Subsystems should be tested after each of the objects and
classes within that subsystem have been tested individually. Existing subsystems,
which were reused or purchased, should be treated as components with unknown
internal structure. That does not mean they should not be tested, on the other hand
it means that they should be tested rigorously, as it is impossible to examine and
walkthrough the internals.
Unit testing may be called component testing. Components that will require
testing include the following:
1. Individual functions or methods within the object.
2. Object classes that have attributes and methods (most all do).
3. Composite components, packages or binary files that will be linked to the
project.
When testing object classes, tests which cover all the features of the object
should be tested (Sommerville
2004
).The tests should be thorough, meaning that
they should cover all possible points of failure as well as input ranges. It is crucial
to include tests out of the scope of the specification to check error handling and not
only check the values for which it is known to work.
• Testing in isolation of all operations associated with the object.
• The setting and interrogation of all attributes associated with the object.
• The exercise of the object in all possible states.
