Testing Software Equipment
A major systems crash angered customers and damaged the telecoms company's reputation for a long period. It took some time for the company to win back customers. Several years ago, the elections suffered a big setback when at the eleventh hour the computer databases crashed. Hundreds of thousands of votes had to be counted by hand. The databanks had been plagued by software testing course bugs, but there was no back-up.
In another well known case, a new airport in the US was delayed for six months because of software testing course problems affecting the baggage collection systems. Client/server software problems are occurring all the time throughout industry, but often these network disasters don't reach the public's ears.
These software testing course fiascoes could badly dent a corporation's image. In the early and middle days of the client/ server revolution, many companies moved too quickly to embrace the open systems environment without enough software contingency plans. A recent survey of the US big corporate networks by Coopers & Lybrand had found that more than 75 per cent of information systems management projects were dogged by quality problems.
Another survey by the Yankee Group on the US found that software testing was now one of the two biggest issues in client/server environments. Conventional manual software testing is slow, tedious, error prone and expensive. The real challenge for big networks, say 500 users, is to test the system for a real-time environment. Testing often becomes the last resort for companies who want to introduce a system quickly into the workplace. Unfortunately, testing is regarded as a bottleneck. Many companies still resorted to the dangerous practice of beta testing the software across networks after it had been installed and in real-time environments, leaving themselves wide open to software bugs and other applications problems. The good news was there had been a significant turnaround by boardrooms which were looking more closely at software testing. By combining the four approaches to automated testing (context-sensitive recording, analogue recording, context sensitive programming and analogue programming) into a single tool provided developers with a comprehensive and robust method of automating the testing process for graphical user interface (GUI) applications. Like a discerning human user, context-sensitive tests commands overcome such variations without stumbling, executing test operations on user interface (UI) elements wherever they are moved to. Such equipment must be easy to carry, hard to break, and simple to use. In addition, it must contain enough on-board intelligence to make the technician using it effective and efficient. While data networks may change and evolve, the basics of maintaining and troubleshooting critical communications links will remain unchanged.
Network Testing Software
|