Arsiv

Etiketler ‘Debugging’

Estimation Methods for Defect Estimation

March 9th, 2010

Accurate defect prediction is useful for planning and management of software testing. The major goal of a software testing process is to find and fix, during debugging, as many defects as possible and release a product with a reasonable reliability.

A trade-off between releasing a product earlier or investing more time on testing is always an issue for the . The clear view of the status of the testing process is crucial to compute the pros and cons of possible alternatives. Time to achieve the established goal and percentage of the goal achieved up to the moment are to determine the status of a software testing process.

Many defect prediction techniques have addressed this important problem by estimating the total number of defects, which then provide the status of a testing process in terms of remaining number of defects in a . The availability of an accurate estimation of the number of defects at early stages of the testing process allows for proper planning of resource usage, estimation of completion time, and current status of the process. Also, an estimate of the number of defects in the product by the time of release, allows the inference of required customer support.

Uncategorized , , , , , , , , , , , , ,

Cisco CCNA / CCNP Certification: Deciphering Ping Results

February 10th, 2010

As you study for your CCNA and CCNP exams, particularly if you’re getting hands-on practice in your home lab or rack rental service, you’re going to be sending a lot of . As a CCNA or CCNP candidate, you know that five exclamation points (!!!!!) as a ping return indicates that you have IP connectivity to the remote destination. Five periods (…..) indicates that you do not have that connectivity.

Unlimited lifetime access Cisco CCNA / CCNP Certification: Deciphering Ping Results

It’s not enough to know that you don’t have IP connectivity to the remote device, you’ve got to know why. Ping is a great first step to , but the results are quite limited. As a CCNA and CCNP, you’ve got to know how to diagnose the problem and resolve it. Just looking at the routing table is not enough – a high-powered Cisco debug, debug , can often show you exactly where the problem is.

WARNING: debug should not be run on any production router without understanding the effect of this command on your router. This command results in a lot of output and can actually lock up a router.

In this case, we’ll run the command on a home lab router that cannot ping 22.2.2.2. The debug will be turned on and another ping sent.

R1#debug

is on

R1#ping 22.2.2.2

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 22.2.2.2, timeout is 2 seconds:

3d23h: IP: s=1.1.1.1 (local), d=22.2.2.2, len 100, unroutable.

R1#undebug all

All possible has been turned off

I’ve edited this output for ; the important word is “unroutable”. This indicates that the packet is not leaving the router because there is no match in the routing table for this destination. We’ll configure a static default route and send the ping again.

R1#ping 22.2.2.2

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 22.2.2.2, timeout is 2 seconds:

U.U.U

is 0 percent (0/5)

That output may surprise those of you who are used to getting five of the same symbol back whenever you send a ping. We got three “U”s back along with two periods. We’ll now run debug and send the ping again.

R1#debug

is on

R1#ping 22.2.2.2

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 22.2.2.2, timeout is 2 seconds:

3d23h: IP: s=172.12.123.1 (local), d=22.2.2.2 (Serial0), len 100, sending

R1#traceroute 22.2.2.2

Type escape sequence to abort.

Tracing the route to 22.2.2.2

1 172.12.123.2 36 msec 36 msec 36 msec

2 172.12.123.2 !H * !H

R1#undebug all

All possible has been turned off

Again, I’ve edited this output. The key word in this output is “sending”, meaning that the packets are leaving the router. The ping return of “U.U.U” is a general indication that the packets are indeed being transmitted, but that a downstream router is having a problem routing the packets. Running traceroute reveals some more interesting return characters! In this case, the downstream router did not have a match for the destination in its routing table.

It’s easy to concentrate on the local router when you’re not getting positive ping returns. When troubleshooting this kind of issue, keep in mind the problem could be on an intermediate router and not on the local router. Use debug to make sure the packets are leaving the local router, and traceroute to determine what downstream router may have the problem. And get used to the fact that and traceroutes can give you some unusual-looking returns!

MCSE | MCSE Training

Incoming search terms for the article:

Uncategorized , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,