Answer Posted / manju

Test Strategy for Middleware and Firmware

We have defined middleware and firmware and understand that
they are different, yet have many characteristics in common
when it comes to testing. The discussion of test strategy
for these types of software will include both middleware
and firmware, and can be extended to test any software
which is not accessed by a user interface.

Early Testing

Early testing will multiply the testing effectiveness of
any software application, regardless of technology.
However, in the world of middleware and firmware early
testing is most critical because finding defects at later
stages carries a higher penalty of rework. This is due to
the extent of integration with hardware and other software.

The problem with early testing in this environment is that
with so many integration dependencies, how does someone
create test harnesses and stubs that allow for an accurate
test? Manually, the job is possible, but can be
overwhelming when there are many interfaces involved. If
you are developing in a language that has tool support for
structural test case design and testing, you may find that
the job can be very easy. Specifically, for C++ and Java,
Parasoft (www.parasoft.com) has a great toolset to design
and perform structural tests, with a feature to
automatically create a test harness and test stubs. Similar
tools are available from International Software Automation
(ISA) www.softwareautomation.com.

Developer Testing

Developer testing is essential to avoid high rework costs.
To the testers, the software is a black box. Only the
developers have the view and access to the code to test all
conditions. In addition, not only are functional cases at
stake, but also the structural tests for memory boundary
violations and memory leaks.

My experience is that developers can test software if the
have a good process to follow, standards to show what is
expected of them in terms of testing, and a way to hold
developers accountable for the quality of their work.
Management must also be making the message loud and clear
that testing is part of the job and that quality is a
shared responsibility between developers, testers, QA, and
management.

An Object-oriented View of Testing

In the object-oriented view of testing, tests are isolated
at a smaller scope, yet can have high complexity due to the
interfaces with other objects. The object-oriented view of
testing must be able to deal with classes, methods, and
attributes and to validate those at a high level of
coverage.

In Shel Siegel's book, "Object-Oriented Software Testing,"
he describes the Hierarchical approach to O-O testing.

"The hierarchical approach is at the heart of the object-
oriented testing system. This test approach uses and builds
upon several well-understood testing techniques, tying them
together into a comprehensive testing system. The
hierarchical approach leverages the fact that "everything
is a system." It defines and applies testing standards for
several levels of software component: objects, classes,
foundation components, and systems. The hierarchical
approach designates as SAFE those components that meet the
testing standards for that kind of component. Once you
designate a component as SAFE, you can integrate it with
other SAFE components to produce the next-level component.
In turn, you test this component to the level of safety
associated with the component level it represents. SAFE is
always a relative state. It depends entirely on the
standards you choose to enforce, your application, your
attitude toward risk, and the specific risks and risk
management practices you adopt in your project. The
hierarchical approach provides guidelines for minimum
safety; you decide what is right for you."


Figure 2 - The Hierarchical Test Approach

Much more could be said about testing middleware and
firmware. This article is intended to provide a strategy
for testing and a starting point to start developing
detailed techniques. My best advice to you is to read the
books on Object-oriented testing by Shel Siegel and Robert
Binder, investigate the available test tools (new ones are
emerging all the time) and work at the developer level to
reinforce the criticality of testing.

what is regression testing, how effectively the QA lead / manager can implement this for product qualification

2113

---

how many types of testings usually flow in different phases of SDLC

2205

---

what are the disadvantages of selenium IDE..?

1599

---

Why is it that a single, all – encompassing metric cannot be developed for programme complexity or programme quality?

3978

---

Lines of code (LOC) and function point counts (FPC) are two measures of the size of a system. Explain the advantages and disadvantages of using these two metrics for measuring systems.

1012

---

is QA expects any level of interaction from development engineer !!!

2054

---

what are the new trends / methodologies in QA for SW product testing

1974

---

Explain waterfall model? what will the testing team do in Requirement phase in this model and what happens in design phase?

1581

---

is all the test cases to be automized !!! if yes / no let explain the reason

2066

---

What are ‘throwaway’ prototypes and ‘evolutionary’ prototypes? How can production of a prototype be controlled and why is this important?

1057

---

I am looking for interview question / technical questions for veritas netbackup.

2020

---

Hi I want to test regarding cookies.. Session should be good for 4 hours and once expired user is returned to login page.. How can i test the session is good for 4 hrs?? Whether i need wait for 4 hours?

2054

---

explain the model(s) of co-ordination you experienced for effective delivery of the product

1941

---

What are the main risk factors which may be encountered in the development of software?

937

---

Explain your daily task as a Manager?

1736

---