Discussion Locked

Behind the Scenes

0 helpful
291 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This is page 2 of the discussion. Read the opening post

291 replies

by rooymans

StickyMinds.com is the information place for software test StickyMinds is the information place for software test, management, and quality assurance professionals. Articles, papers, links, books, tools, forum. StickyMinds.com is the information place for software test Title: The Practical Organization of Automated Software Testing Title: Graybox Software Testing in the Real World in Real-Time

This post originally appeared on an external website

by rooymans

 

Frost honored companies for outstanding performance at its second annual Excellence in Mobile Communications Banquet, held last week in Las Vegas, Nevada. The banquet recognized 21 companies for innovative developments that deliver unparalleled insight on wireless and mobile strategy, technology, platforms and services. Innovations spanned WiMax, UWB, LBS, unified communications and many other mobile technologies as well as applications, such as life sciences and CRM.

Related...

[CRM - Technology Updates]

This post originally appeared on an external website

by rooymans

Israeli vendor Alvarion announced today it has won a US$1.5 million contract from Cable and Wireless in the Falkland Islands to deploy a GSM network. Alvarion's GSM system offers distributed architecture designed for small to medium size GSM networks. ... Related... [Daily News as it breaks from telecoms.com]

This post originally appeared on an external website

by rooymans

Finnish vendor Nokia announced today it has signed a framework agreement with Danish operator TDC to supply a WCDMA radio access network, while continuing to supply GSM base station subsystem infrastructure to TDC. Under the agreement, Nokia will deliver GSM base station subsystem and WCDMA radio access network infrastructure. Nokia... Related... [Daily News as it breaks from telecoms.com]

This post originally appeared on an external website

by rooymans

Dutch operator KPN today introduced its no frills prepay offering, Simyo, in the Netherlands, following the service's success in Germany. The starter package costs Eur5 (US$6) and consists of a free SIM card with Eur5 credit. Calls costs Eur0.18 per minute to all networks, while SMSes cost Eur0.09. ... Related... [Daily News as it breaks from telecoms.com]

This post originally appeared on an external website

by rooymans

Hutchison Telecommunications International Limited yesterday announced that Hutchison Essar, its joint venture in India with Essar Teleholdings, has entered into an agreement to acquire rival Indian operators BPL Mobile Communications and BPL Mobile Cellular, as well as Essar Spacetel, another mobile operator that has applied for licenses in seven license... Related... [Daily News as it breaks

This post originally appeared on an external website

by rooymans

The GSM Association (GSMA) today announced that it has once again selected U.S. vendor Motorola to deliver a portfolio of handsets targeted at driving uptake of mobile services in developing markets. In phase two of the GSMA's Emerging Market Handset program, Motorola has been selected to deliver sub-US$30 devices,... Related... [Daily News as it breaks from telecoms.com]

This post originally appeared on an external website

by rooymans

O2 announced today that its total number of UK subscribers passed 15 million during 2Q05. In a pre close update statement before the release of the operator's interim results for the six months to end-September, O2 also revealed the Tesco mobile joint venture MVNO had over 750,000 subscribers. Underlying ARPU... Related... [Daily News as it breaks from telecoms.com]

This post originally appeared on an external website

by rooymans

Swedish vendor Ericsson announced today it has been awarded a contract by Libyan operator Al Madar to expand the operators GSM network using Ericsson's Mobile Softswitch solution. Under the deal Ericsson will supply a complete GSM turnkey core network, including mobile softswitch, radio network, a charging system and GPRS capability.... Related... [Daily News as it breaks from telecoms.com]

This post originally appeared on an external website

by rooymans

UK operator O2 today announced that it would make i-mode available in the country from October 1, on both its GPRS and UMTS networks and to postpaid and prepaid subscribers. The move will be followed by the introduction of i-mode by O2 Ireland next week, while the German operation will... Related... [Daily News as it breaks from telecoms.com]

This post originally appeared on an external website

by rooymans

Unfortunately, in the real world you will never see a project perfectly follow any of the development models. You will never be given a thoroughly detailed specification that perfectly meets the customers needs and you will never have enough time to do all the testing you need to do. It just doesnt happen. This chapter will help you understand that software testing doesnt alway go perfectly, and

This post originally appeared on an external website

by rooymans

Orange announced today the launch of a new PC data card that automatically detects the fastest network available starting with WiFi, 3G through to EDGE and GPRS as part of its 'Business Everywhere' solution. Trials of the offering have already commenced and the service will be available in France and... Related... [Daily News as it breaks from telecoms.com]

This post originally appeared on an external website

by rooymans

mobilkom Austria announced yesterday it is introducing a new PC data card which supports GSM/GPRS, EDGE and UMTS. The data card, which will have an upgrade option to HSDPA, will be on sale online for Eur99 (US$119) from October 3 and in stores from October 17. ... Related... [Daily News as it breaks from telecoms.com]

This post originally appeared on an external website

by rooymans

Streaming media firm RealNetworks yesterday announced that it has been selected as the solution provider for Cingular Wireless' next generation video service, using its newly unveiled Helix OnlineTV application, which offers personal interactive TV to consumers' handsets or PCs. Real will provide Cingular with a comprehensive video solution including... Related... [Daily News as it breaks from

This post originally appeared on an external website

by rooymans

Something I've been experimenting with recently is Test-Driven Design (TDD) for user interfaces (UI). In brief (see Wikipedia for further details), with TDD you write a test, run it to be sure it fails, and then write just enough code to make it pass. The power here is that you are forced to specify what should happen before you write the code to make it happen, so you typically write simpler

This post originally appeared on an external website

by rooymans

Businesses across Europe claim that software testing is a strategically important part of new product and service delivery. Yet despite this, testing tends to remain the sole responsibility of IT managers rather than business managers, finds new independent research published yesterday by LogicaCMG. Related... [Quality Assurance - Technology Updates]

This post originally appeared on an external website

by rooymans

Changes to Product features can happen many times during a product development lifecycle. These may be driven by change of customer requirements, design changes or some times as late as customer acceptance tests. Many times, making necessary changes reported by customers can be crucial. In such scenarios test cases drawn by Test Engineers can become obsolete rendering the whole effort in test

This post originally appeared on an external website

by rooymans

The Scrum methodology can pose a challenge for software testers who are used to more traditional waterfall-inspired development processes. Jonathan Kohl relates his experiences working on Scrum teams who found some clear advantages in changing their methods. Related... [Quality Assurance - Technology Updates]

This post originally appeared on an external website

by rooymans

T-Mobile Austria announced today it has struck an agreement to provide its WiFi HotSpot service in eight of the nine Starbucks Coffee Houses in Austria. With this deal, T-Mobile and Starbucks now have agreements in every country both companies are active, with the HotSpot service available at over 4,000 Starbucks... Related... [Daily News as it breaks from telecoms.com]

This post originally appeared on an external website

by rooymans

T-Mobile UK today unveiled its long awaited consumer 3G strategy, firmly placing the focus on a mobile Internet drive to be spearheaded by its web 'n' walk service. The web 'n' walk offering will be available from today over T-Mobile's GPRS and UMTS networks, launching with five handsets initially,... Related... [Daily News as it breaks from telecoms.com]

This post originally appeared on an external website

by rooymans

Dutch operator KPN today announced the completion of the takeover of local cellco Telfort, for which it paid Eur980 million (US$1.1 billion) back in June. In line with KPN's strategy of using multiple brands to serve specific segments of the mobile market, KPN said it will continue to use the... Related... [Daily News as it breaks from telecoms.com]

This post originally appeared on an external website

by rooymans

By Harry Suhartono JAKARTA, Oct 6 (Reuters) - Shares of Indonesia's third-largest mobile phone operator, PT Excelcomindo Pratama Tbk (EXCL.JK: , , ), jumped 18 percent on Thursday after the company predicted it would be profitable next year. Related... [Moreover Technologies - Telecom news]

This post originally appeared on an external website

by rooymans

Through this agreement, Nokia will be able to preload their Series 60 and Symbian OS based mobile devices with Symantec's mobile security solutions, offering increased protection for consumer and business users against mobile malware threats. ' Related... [Moreover Technologies - Telecom news]

This post originally appeared on an external website

by rooymans

. The folks at CRIM Software Test Center sponsor a web site for the FAQ at Automated and Manual Software Testing Tools and Services Software testing products and services. Provides tools and outsourced services for QA testing. We specialize in manual and automated testing of software for Related... [Software Testing]

This post originally appeared on an external website

by rooymans

Amazon.com: Testing Computer Software, 2nd Edition: Books Amazon.com: Testing Computer Software, 2nd Edition: Books by Cem Kaner,Jack Falk,Hung Q. Nguyen. Software Testing Institute Quality publications, industry research and online services for the software development and testing professional. Related... [Software Testing]

This post originally appeared on an external website

by rooymans

Hutchison Whampoa today announced that, as of October 7, its global 3G customer base surpassed the 10 million subscriber point. Hutchison provides services under the 3 brand in nine markets to date: Australia, Austria, Denmark, Hong Kong, Ireland, Israel, Italy, Sweden and the UK, and today claimed to have marketed... Related... [Daily News as it breaks from telecoms.com]

This post originally appeared on an external website

by rooymans

Telecom Italia has announced plans to accelerate the integration process of its fixed line activities with mobile unit Telecom Italia Mobile, in a bid to sooner develop integrated offers and deliver efficiency gains. Under the new structure, CEO Riccardo Ruggiero, will be responsible for operations, CEO Carlo Buora, will be... Related... [Daily News as it breaks from telecoms.com]

This post originally appeared on an external website

by rooymans

Italian operator Telecom Italia Mobile (TIM) and local media firm Mediaset have announced the reaching of an agreement for commercial launch of digital terrestrial TV on mobile phones using DVB-H technology. TIM claims to be the first Italian mobile operator to commit itself to the provision of DVB-H services,... Related... [Daily News as it breaks from telecoms.com]

This post originally appeared on an external website

by rooymans

Execution of tests is completed by following the test documents in a methodical manner. As each test procedure is performed, an entry is recorded in a test execution log to note the execution of the procedure and whether or not the test procedure uncovered any defects. Checkpoint meetings are held throughout the execution phase. Checkpoint meetings are held daily, if required, to address and

This post originally appeared on an external website

by rooymans

Analysts have blasted some CRM implementations as too big, too expensive and too difficult to measure in terms of success -- or payback. And vendors such as Oracle and Amdocs say they have learned their lessons, as have service providers. But enthusiasm for CRM solutions has not waned. Related... [CRM - Technology Updates]

This post originally appeared on an external website

by rooymans

Why IT Salespeople Hate Customer Relationship Management (CRM) Systems: "CRM and Sales Force Automaton (SFA) tools have been actively marketed for the last ten years and have become a stable business purchase for both the SMB market and the Global 1000. Yet in talking with IT salespeople here in North America and overseas, we constantly receive input from salespeople that they do not like to use

This post originally appeared on an external website

by rooymans

3 UK reveals new mobile TV line up: "3 UK announced the launch of an enhanced mobile TV service today, with channels in the package including CNN, ITN and Bravo. The channels, which are live now and available for a subscription of ?5 (US$8.74) a month, will complement 3's TV service which offers a range of formats, from..."

This post originally appeared on an external website

by rooymans

Systems that work well during development, deployed on a small scale, can fail to meet performance goals when the deployment is scaled up to support real levels of use.
An apposite example of this comes from a major blue chip company that recently outsourced the development of an innovative high technology platform. Though development was behind schedule this was deemed acceptable. The system

This post originally appeared on an external website

by rooymans

For a conventional software tester, an Extreme Programming project may be an intimidating challenge. Testers often find that theyre not welcome on XP projects, but Jonathan Kohl shares how skilled testing can overcome such difficulties. Jonathan discusses lessons he learned from working on two different XP project teams, only one of which initially welcomed his testing and feedback.
Link

This post originally appeared on an external website

by rooymans

Japanese operator NTT DoCoMo today announced it has transferred its interest in Dutch telecommunications company KPN Mobile to parent company KPN. Under the agreement, DoCoMo will transfer approximately 2.16% of KPN Mobile's outstanding shares for around Eur5 million (US$5.9 million), and as a result of the agreement, will record...
Link

This post originally appeared on an external website

by rooymans

easyGroup, the no frills operation owned by entrepreneur Stelios Haji-Ioannou, will launch MVNO services under the easyMobile brand in the Netherlands, October 25. easyMobile, which is a collaboration between Telmore International Holding - owned by Denmark's TDC - and the easyGroup, will utilize the network of local incumbent Telfort....
Link

This post originally appeared on an external website

by rooymans

Disaster Recovery is not Business Continuity. Many companies don't have full business continuity plans. They may believe they do have business continuity plans but they really have a disaster recovery plan, usually meaning that they have alternative premises and possibly equipment that can be used in the case of a full scale disaster. Business continuity covers far more than just the IT systems.

This post originally appeared on an external website

by rooymans

People often equate load testing with performance testing. Load testing is seen as a way of answering the question ?How fast does the system respond?? This view then tends to mean that load testing is seen as an end of project activity. Only at the end of development will we have the final implementation for performance testing and so we can confirm only then that it performs quickly enough in the real world and smoothly transition into live service.

Wrong approach! This is extremely risky and misses out on the many benefits of starting load testing early and applying it throughout the project. With this approach does the system sail through load testing and transition smoothly into service? Occasionally yes. But more frequently the system starts to fail as load starts to be applied, even with small increases in volume.. For the first time there are concurrent demands on the system and arbitration over resources is required. Paths through code that have never been executed are triggered, situations arise that nobody really thought through. Transactions fail. Systems crash. After these problems are fixed and more load is applied in a test, we then encounter problems like resource exhaustion, buffer overflows, timeouts and inconsistent behaviour. The real work needed to turn a functional pre-production system into a robust solution has only just begun.

Examples abound of products that failed when load testing started and, after lots of effort, stress and expenditure, have been shelved. Worse still are the ones that missed load testing altogether and failed dramatically during live operation. An internet portal developer recently stopped development of a new service, one that had completed functional development, when load testing revealed fundamental structural problems and inefficient coding which led to a poorly performing and unstable system.

So what should you do to avoid these risks? We all know it is better to find faults early when they cost far less to fix yet load testing is still left until as late as possible. The types of faults it finds frequently need architectural changes and major rewrites which are by then are hugely expensive to implement. The answer is that you should start early. Different forms of load testing should be repeatedly applied throughout the project to identify problems early and to check that the system is not going off track.

This is a natural extension of the practice of test led development. Test led development, where automated tests are written first and code must pass these tests as it is developed, offers major benefits. However, in its current form, the focus of this testing is on functionality. As it evolves the functional status of the software is always known and hence manageable, functional faults are nipped in the bud avoiding high cost fixes, the functional risk is greatly reduced. Not so other risks. If a project performs early and continuous load testing it gets much wider and comprehensive risk reduction. To make this effective:

  1. Study the system and perform a risk analysis to help to order the threats to the system, this will help you to prioritise load testing activities.
  2. Collect data to allow comparison of the efficiency of different builds. This permits monitoring of the long term trend, ?Is the system using more and more processor time to do the same work?? This data can be used to predict resource requirements at different levels of demand and so support scalability predictions.
  3. Execute tests that aim to assess the behaviour of the system and to trigger faults under load. Use workloads that simulate expected patterns of demand to observe the aggregate behaviour of the system. Use specially targeted extreme workloads to probe the vulnerabilities of the system.
  4. Include the full spectrum of load tests into the test suite. This means performance testing with typical and busy period work loads; stress testing to check both atypical demand spikes and resource exhaustion impacts; endurance testing that uses both operational period and cumulative operation tests; reliability testing that runs lots of transactions and then checks whether occasional transactions fail; concurrency testing of two users working on the same account at the same time.
  5. Design measurement activities as scientists would design an experiment, design them to provide data that can be analysed. Sample the system under different steady state workloads to provide multiple data sets to support interpolation. Chose the workloads to permit estimation of the resource costs for each transaction type.
  6. Target the middleware first with generic activities and evolve the suite as functionality is developed. Start early and then test each incremental release of the system, firstly with the previous suite and then with a modified suite that addresses new functionality.
  7. Invest the time and resources to work at a representative scale. Maybe the test bed can?t be full scale but it should not be two orders of magnitude smaller than the intended system. Be smart and innovative to use resources effectively to provide an appropriate scale test bed. The costs that will be incurred if this is not done will far exceed the cost of providing the test bed.
  8. Don?t delay; test an increment as soon as possible. Don?t skip one or you?ll end up skipping them all. Compare the measurements and behaviour with the previous one, is it better or worse?
  9. Provide a background load for functional testing. Features that work offload may fail when the system has other things to think about.
  10. Consider occasional events such as server failures and reconfiguration of the system. Do these need to be tested under load?

In conclusion, you need to incorporate load testing throughout the development process. Leaving load testing until the final run in to live service is a recipe for disaster. If this became common practice then a lot more applications and systems that work would be delivered on time and to budget.

? Acutest Ltd 2005

About Acutest

Acutest is a consultancy specialising in testing software, IT and technology-enabled change. Acutest provides a full portfolio of outsourced software testing services. Popular services include performance testing and business continuity testing.

Acutest Ltd
Blackwell House
Guildhall Yard
London EC2V 5AE 
Website: http://www.acutest.co.uk/

Link

This post originally appeared on an external website

by rooymans

People often equate load testing with performance testing. Load testing is seen as a way of answering the question ?How fast does the system respond?? This view then tends to mean that load testing is seen as an end of project activity. Only at the end of development will we have the final implementation for performance testing and so we can confirm only then that it performs quickly enough in the real world and smoothly transition into live service.

Wrong approach! This is extremely risky and misses out on the many benefits of starting load testing early and applying it throughout the project. With this approach does the system sail through load testing and transition smoothly into service? Occasionally yes. But more frequently the system starts to fail as load starts to be applied, even with small increases in volume.. For the first time there are concurrent demands on the system and arbitration over resources is required. Paths through code that have never been executed are triggered, situations arise that nobody really thought through. Transactions fail. Systems crash. After these problems are fixed and more load is applied in a test, we then encounter problems like resource exhaustion, buffer overflows, timeouts and inconsistent behaviour. The real work needed to turn a functional pre-production system into a robust solution has only just begun.

Examples abound of products that failed when load testing started and, after lots of effort, stress and expenditure, have been shelved. Worse still are the ones that missed load testing altogether and failed dramatically during live operation. An internet portal developer recently stopped development of a new service, one that had completed functional development, when load testing revealed fundamental structural problems and inefficient coding which led to a poorly performing and unstable system.

So what should you do to avoid these risks? We all know it is better to find faults early when they cost far less to fix yet load testing is still left until as late as possible. The types of faults it finds frequently need architectural changes and major rewrites which are by then are hugely expensive to implement. The answer is that you should start early. Different forms of load testing should be repeatedly applied throughout the project to identify problems early and to check that the system is not going off track.

This is a natural extension of the practice of test led development. Test led development, where automated tests are written first and code must pass these tests as it is developed, offers major benefits. However, in its current form, the focus of this testing is on functionality. As it evolves the functional status of the software is always known and hence manageable, functional faults are nipped in the bud avoiding high cost fixes, the functional risk is greatly reduced. Not so other risks. If a project performs early and continuous load testing it gets much wider and comprehensive risk reduction. To make this effective:

  1. Study the system and perform a risk analysis to help to order the threats to the system, this will help you to prioritise load testing activities.
  2. Collect data to allow comparison of the efficiency of different builds. This permits monitoring of the long term trend, ?Is the system using more and more processor time to do the same work?? This data can be used to predict resource requirements at different levels of demand and so support scalability predictions.
  3. Execute tests that aim to assess the behaviour of the system and to trigger faults under load. Use workloads that simulate expected patterns of demand to observe the aggregate behaviour of the system. Use specially targeted extreme workloads to probe the vulnerabilities of the system.
  4. Include the full spectrum of load tests into the test suite. This means performance testing with typical and busy period work loads; stress testing to check both atypical demand spikes and resource exhaustion impacts; endurance testing that uses both operational period and cumulative operation tests; reliability testing that runs lots of transactions and then checks whether occasional transactions fail; concurrency testing of two users working on the same account at the same time.
  5. Design measurement activities as scientists would design an experiment, design them to provide data that can be analysed. Sample the system under different steady state workloads to provide multiple data sets to support interpolation. Chose the workloads to permit estimation of the resource costs for each transaction type.
  6. Target the middleware first with generic activities and evolve the suite as functionality is developed. Start early and then test each incremental release of the system, firstly with the previous suite and then with a modified suite that addresses new functionality.
  7. Invest the time and resources to work at a representative scale. Maybe the test bed can?t be full scale but it should not be two orders of magnitude smaller than the intended system. Be smart and innovative to use resources effectively to provide an appropriate scale test bed. The costs that will be incurred if this is not done will far exceed the cost of providing the test bed.
  8. Don?t delay; test an increment as soon as possible. Don?t skip one or you?ll end up skipping them all. Compare the measurements and behaviour with the previous one, is it better or worse?
  9. Provide a background load for functional testing. Features that work offload may fail when the system has other things to think about.
  10. Consider occasional events such as server failures and reconfiguration of the system. Do these need to be tested under load?

In conclusion, you need to incorporate load testing throughout the development process. Leaving load testing until the final run in to live service is a recipe for disaster. If this became common practice then a lot more applications and systems that work would be delivered on time and to budget.

? Acutest Ltd 2005

About Acutest

Acutest is a consultancy specialising in testing software, IT and technology-enabled change. Acutest provides a full portfolio of outsourced software testing services. Popular services include performance testing and business continuity testing.

Acutest Ltd
Blackwell House
Guildhall Yard
London EC2V 5AE 
Website: http://www.acutest.co.uk/

Link

This post originally appeared on an external website

by rooymans

People often equate load testing with performance testing. Load testing is seen as a way of answering the question ?How fast does the system respond?? This view then tends to mean that load testing is seen as an end of project activity. Only at the end of development will we have the final implementation for performance testing and so we can confirm only then that it performs quickly enough in the real world and smoothly transition into live service.

Wrong approach! This is extremely risky and misses out on the many benefits of starting load testing early and applying it throughout the project. With this approach does the system sail through load testing and transition smoothly into service? Occasionally yes. But more frequently the system starts to fail as load starts to be applied, even with small increases in volume.. For the first time there are concurrent demands on the system and arbitration over resources is required. Paths through code that have never been executed are triggered, situations arise that nobody really thought through. Transactions fail. Systems crash. After these problems are fixed and more load is applied in a test, we then encounter problems like resource exhaustion, buffer overflows, timeouts and inconsistent behaviour. The real work needed to turn a functional pre-production system into a robust solution has only just begun.

Examples abound of products that failed when load testing started and, after lots of effort, stress and expenditure, have been shelved. Worse still are the ones that missed load testing altogether and failed dramatically during live operation. An internet portal developer recently stopped development of a new service, one that had completed functional development, when load testing revealed fundamental structural problems and inefficient coding which led to a poorly performing and unstable system.

So what should you do to avoid these risks? We all know it is better to find faults early when they cost far less to fix yet load testing is still left until as late as possible. The types of faults it finds frequently need architectural changes and major rewrites which are by then are hugely expensive to implement. The answer is that you should start early. Different forms of load testing should be repeatedly applied throughout the project to identify problems early and to check that the system is not going off track.

This is a natural extension of the practice of test led development. Test led development, where automated tests are written first and code must pass these tests as it is developed, offers major benefits. However, in its current form, the focus of this testing is on functionality. As it evolves the functional status of the software is always known and hence manageable, functional faults are nipped in the bud avoiding high cost fixes, the functional risk is greatly reduced. Not so other risks. If a project performs early and continuous load testing it gets much wider and comprehensive risk reduction. To make this effective:

  1. Study the system and perform a risk analysis to help to order the threats to the system, this will help you to prioritise load testing activities.
  2. Collect data to allow comparison of the efficiency of different builds. This permits monitoring of the long term trend, ?Is the system using more and more processor time to do the same work?? This data can be used to predict resource requirements at different levels of demand and so support scalability predictions.
  3. Execute tests that aim to assess the behaviour of the system and to trigger faults under load. Use workloads that simulate expected patterns of demand to observe the aggregate behaviour of the system. Use specially targeted extreme workloads to probe the vulnerabilities of the system.
  4. Include the full spectrum of load tests into the test suite. This means performance testing with typical and busy period work loads; stress testing to check both atypical demand spikes and resource exhaustion impacts; endurance testing that uses both operational period and cumulative operation tests; reliability testing that runs lots of transactions and then checks whether occasional transactions fail; concurrency testing of two users working on the same account at the same time.
  5. Design measurement activities as scientists would design an experiment, design them to provide data that can be analysed. Sample the system under different steady state workloads to provide multiple data sets to support interpolation. Chose the workloads to permit estimation of the resource costs for each transaction type.
  6. Target the middleware first with generic activities and evolve the suite as functionality is developed. Start early and then test each incremental release of the system, firstly with the previous suite and then with a modified suite that addresses new functionality.
  7. Invest the time and resources to work at a representative scale. Maybe the test bed can?t be full scale but it should not be two orders of magnitude smaller than the intended system. Be smart and innovative to use resources effectively to provide an appropriate scale test bed. The costs that will be incurred if this is not done will far exceed the cost of providing the test bed.
  8. Don?t delay; test an increment as soon as possible. Don?t skip one or you?ll end up skipping them all. Compare the measurements and behaviour with the previous one, is it better or worse?
  9. Provide a background load for functional testing. Features that work offload may fail when the system has other things to think about.
  10. Consider occasional events such as server failures and reconfiguration of the system. Do these need to be tested under load?

In conclusion, you need to incorporate load testing throughout the development process. Leaving load testing until the final run in to live service is a recipe for disaster. If this became common practice then a lot more applications and systems that work would be delivered on time and to budget.

? Acutest Ltd 2005

About Acutest

Acutest is a consultancy specialising in testing software, IT and technology-enabled change. Acutest provides a full portfolio of outsourced software testing services. Popular services include performance testing and business continuity testing.

Acutest Ltd
Blackwell House
Guildhall Yard
London EC2V 5AE 
Website: http://www.acutest.co.uk/

Link

This post originally appeared on an external website