Behind the Scenes
This is page 3 of the discussion. Read the opening post
After Hours
This is page 3 of the discussion. Read the opening post
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:
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
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:
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
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:
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
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:
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
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:
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
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:
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
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:
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
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:
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
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:
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
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:
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
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:
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
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
by rooymans
Microsoft has released what its calling its Early Adopters Program (EAP) Microsoft CRM 3.0 beta to certified partners and customers, as of this week. Looks like the final product wont be released to manufacturing until the first quarter of 2006 now.
Link
by rooymans
2 in San Diego. SAS will be in Booth 3 showcasing its suite of customer intelligence solutions.
Link
by rooymans
Siebel Systems Inc. said Wednesday that its third quarter net income soared 89 percent to $34.7 million, or 6 cents a share. San Mateo-based Siebel (NASDAQ:SEBL) , which has agreed to be acquired by Redwood City-based Oracle Corp. (
Link
by rooymans
The growing popularity of free Internet telephony software from Skype Technologies could pose the same kind of security challenges for companies that other peer-to-peer technologies have created in recent years, security experts said.
Link
by rooymans
New Delhi, Oct. 28: World's leading mobile operator, Vodafone Group Plc., is buying 10 per cent of Indian private telecom major Bharti Tele-Ventures Ltd for a sum of $1.5 billion.
Link
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
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
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
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
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
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
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
by rooymans
Spanish operator Telefonica today announced that it has agreed to make a cash offer to purchase UK-based mobile operator O2 for approximately ?17.7 billion (US$31.5 billion). Telefonica said the move would allow it to provide enhanced scale by entering Germany and the UK with a critical mass, and would...
Link
by rooymans
This is a concept I can't stress enough: test automation is software development. There really is no getting around it. Even if we use a record/playback testing tool, some sort of code is generated behind the scenes. This is nothing...
Link
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
by rooymans
Spanish operator Telefonica Moviles today reported consolidated net income for the quarter to end-September increased 24% year on year to reach Eur614.9 million (US$738 million), while revenues increased 45.9% year on year to Eur4.3 billion. Operating income at the operators home market remained flat year on year at Eur1.1 billion,...
Link
by rooymans
BONN - Phone giant Deutsche Telekom said Wednesday it would shed nearly one fifth of its German workforce, or 32,000 staff, over the next three years, mainly because of losses at its German fixed- line division.
Link
by rooymans
Dutch telco KPN announced today that total operating revenues from its mobile operations stood at Eur1.44 billion (US$1.6 billion) for the three months to end-September, compared with Eur1.35 billion last year, while total operating profit for the mobile business dropped to Eur196 million in 3Q05 from Eur221 million in 3Q04....
Link
by rooymans
Hungarian telco Magyar Telekom's Extraordinary General Meeting has approved the intended merger of mobile operator T-Mobile Hungary and Magyar Telekom as submitted by the Board.
Link
by rooymans
International Tuesday November 8, 2:31 PM Singapore Telecom mobile users in Asia top 74 million Singapore Telecommunications Ltd. (
Link
by rooymans
SAN FRANCISCO (MarketWatch) -- Shares of Yahoo Inc. closed fractionally higher Monday, participating an advance by the wider Internet group, after the online-media giant unveiled partnerships with SBC Communications Inc. and TiVo Inc.
Link
by rooymans
Microsoft Chairman Bill Gates sent a memo last month alerting his executives to the dramatic changes facing the software business. Two days earlier, Chief Technical Officer Ray Ozzie, who is leading the services push, outlined the challenges as he saw them in his own memo. In it, Ozzie asked, How can we utilize our extant products and our knowledge of the broad historical adoption of forms-based
by rooymans
Germany's Federal Office for Security in Information Technology is warning of potential VoIP security risks in a study presented at Systems IT conference.
Link
by rooymans
UK MVNO Virgin Mobile today announced total revenues rose 7% year on year to ?274.6 million (US$471.7 million) for the six months to end-September, while service revenues were also up 9% year on year to ?250.8 million. Operating profit at the MVNO rocketed 27% year on year to ?45.5 million...
Link
by rooymans
LogicaCMG announced today it has won a contract to provide its uOne next generation voicemail and videomail solution to Portuguese operator Optimus. The service will run from the two major cities in Portugal, Porto and Lisbon. LogicaCMG's uOne solution will also allow Optimus to support their legacy voicemail solution, enabling...
Link
by rooymans
Finnish vendor Nokia announced today it has signed a definitive agreement to acquire mobile application and messaging provider Intellisync. Under the terms of the agreement Intellisync stockholders will receive US$5.25 per share in cash for each Intellisync common share, giving the company an enterprise value of around US$430 million. The...
Link
by rooymans
I suspect this is something many of us give lip service to: unit testing. There has been some discussion over the last few days on some ColdFusion lists about unit testing frameworks.Ive been using Paul Kenneys CFCUnit on and off (and, mea culp...
Link
by rooymans
Thu 24 Nov 2005 Printer friendly Send to friend Vodafone quits Man Utd shirts VODAFONE has ended its 36 million shirt sponsorship deal with Manchester United two years early.
Link
by rooymans
23 (Bloomberg) -- Vodafone Group Plc, the world's largest mobile-phone service provider, said it will end a sponsorship accord with Manchester United two years earlier than planned and will endorse Europe's Champions League competition.
Link
by rooymans
Singapore Telecommunications' Australian unit Optus has intensified negotiations to buy AAPT from Telecom New Zealand in a deal that could be worth up to 850 million dollars (625 million US), it was reported.
Link
by rooymans
TELECOM New Zealand has been forced to dampen speculation that it's close to sealing a deal to sell its Australian subsidiary AAPT.
Link
by rooymans
Lachlan Murdoch has conceded he remembers little about his directorship of One.Tel, the failed phone company in which his family's News Corporation invested close to $A600 million.
Link
by rooymans
FRANKFURT (Reuters) - Deutsche Telekom is willing to give rivals access to a 3 billion-euro super-fast Internet network it plans to build in Germany, Chief Executive Kai-Uwe Ricke told a magazine.
Link
by rooymans
When Malcolm Glazer borrowed 500m to buy Manchester United, he did so in expectation of making big profits from the biggest club in the world's favourite game.
Link
by rooymans
Tatas telecommunications unit, Videsh Sanchar Nigam, plans to invest in the countrys long distance and wireless service, the Business Standard newspaper quoted company officials as saying.
Link
by rooymans
Briefs: Telecom denies sale of Aussie subsidiary : Font size: - N Telecom New Zealand says it is not on the verge of selling its Australian subsidiary despite media reports to the contrary.
Link
by rooymans
24 (Bloomberg) -- ABN Amro Holding NV, Goldman Sachs JBWere Pty and UBS AG have been hired by Australia's government to sell its 51.8 percent stake in Telstra Corp.,
Link
by rooymans
Testing cannot ensure complete eradication of errors. Various types of Testing have their own limitations. Consider Exhaustive black box and white box testing, which are practically not "Exhaustive" to the verbose as they are required to be, owing to the resource factors. While testing a Software Product, one of the most important things is the design of effective test cases. A Tester tries to
by rooymans
15 Dec 2005, 09:12 GMT - Under the terms of the five-year, 500m-euro ($597m) deal, MCI will manage the bank's global data network and firewall platforms supporting more than 6,000 locations in 25 countries.
Link
by rooymans
Laut dem "Kurier" soll der Deal bereits gestern Donnerstag ?ber die B?hne gegangen sein ? Der K?ufer ist noch unbekannt, die Inode-Gesch?ftsleitung will zu den Ger?chten erst am Dienstag Stellung nehmen.
Link
by rooymans
I?ve just stumbled on a new-to-me wiki on software testing. www.softwaretestingwiki.com
Link
by rooymans
Everybody?s talking about unit testing. You want to get into the game, but you don?t want it to take up all your development time and energy. Fortunately, Roy Osherove is here to dispel some testing myths and put you on the road to efficient unit testing.
Link
by rooymans
Agile methodologies are known to work fine for small projects, if approached correctly, still there is some argues about their scalability to large projects. I believe that the root cause of the issues is not the size of the project. It is the business size/goal. Contributing issue is technology complexity. Those are my assumptions ? mostly theoretic and only partly based on experience. More over
by ricki henry
Anything that works for small projects should work for large projects since one of your first objectives in a large project is to break it down into smaller deliverables, i.e. smaller projects. The failure of any methodology with a large project is rarely the methodology but more frequently the analysis-paralysis that you see with large projects. This means that no matter what methodology you use, it will "not work". The major obstacle in breaking larger projects down is the argument that "if we don't know all of the requirements up front, the databases we design may not work causing major redo costs", and "if we break it down we'll be doing duplicate testing which will cost more and take more time". Well folks, break it down into smaller deliverable and do your CBA for each deliverable!. Assume there will be "redo costs", yes, there will be retesting costs. So if the business benefits of early deployment outweigh the costs proceed, if not, don't and combine deliverables until you have the smallest amount possible that will bring the benefit to justify the costs. In smaller enhancement projects we don't bemoan the fact that if we had know about the current project with the last enhancement we could have saved development costs, testing costs and reduced costs of adding new data, do we?
ricki henry (rickihenry@hotmail.com) sr. project manager with 15 years experience
by jslarochelle
The idea that you can break a large project into small iterations that can be managed the same way as the iterations in a small project is too simplistic. For one thing, in a truly large project you will get personnel turnover that is not present in small project and that requires better documentation ( requirements, design) than in a small project.
by a contractor
What is wrong with better documentation? If the large project had come through as a series of smaller requests, the same problems would still be there. Ricki is on the moeny and jslarochelle is a classic IT monolithic maniframe thinker. In today's world you have to be able to not only provide value very quickly, but be able to bring a large project down to a minimal staffing level or close it down because business resources are needed elsewhere. PM that can live in that world are working and making money. Classic IT, monolithic, maniframe thinking PM and consultants are on the street or working in environments that can not continue to support that way of doing business. Learn to be Agile or start looking for another line of work.
by jslarochelle
A contractor is certainly right when he says "learn to be Agile" and I do embrace Agile methodologies. However, I think the most successfull people will adapt and know when to move away from Agile into more formal methods when needed. Fortunatly most of us will rarely have to move very far away from the Agile side of the spectrum because it is appropriate for a large set of projects. I still think that those that stick fanatically to Agile methods even when not appropriate will suffer needlessly.
I think the more you know the better you are at surviving in the software business and that includes Agile methodologies as well as more formal and heaviweight methods. And again moving away from Agile and using more formal methods doesn't mean moving to the other extreme.
by rooymans
The Compuware Application Reliability Solution and Compuware QACenter Enterprise Edition provide centralized test asset repositories, decentralized test management, requirements analysis and optimized testing.
Link
by rooymans
The wildly successful pixel-powered Web page created by British university student Alex Tew has come under intense attacks this week trying to knock the profitable site off-line.
Link
by rooymans
AOL co-founder Steve Case thinks Time Warner should be split up and AOL spun off as a separate company. His views were published in a column in The Washington Post.
Link
by rooymans
Swiss operator Swisscom announced today its Solutions unit will acquire some of Siemens Switzerland's converged solutions business for SFr25 million (US$3.2 million). As part of the deal, Swisscom Solutions will take over the support and care of medium and large business customers from Siemens Switzerland; and 120 service and sales...
Link
by rooymans
UK MVNO Virgin Mobile said that it has received a revised offer from cable company NTL. The company did not say how much the new offer is worth, but reports indicate NTL may have stepped up itsbid from ?834 million (US$1.4 billion), or ?3.23 per share, to ?907 million, or...
Link
by rooymans
Die EU-Kommission hat erhebliche Bedenken gegen die ?bernahme des viertgr??ten ?sterreichischen Mobilfunkanbieters Telering durch T-Mobile.
Link
by rooymans
Mobile operator Orange currently has over 300,000 3G customers in the UK and expects that figure to rise to 1.5 million by the end of 2006.
Link
by rooymans
German vendor Siemens today said it has been contracted by Indonesian operator Hutchison Telecom Indonesia to build, implement, operate and maintain its forthcoming GSM/WCDMA network. Hutchison Whampoa struck an agreement in March to acquire a 60% equity stake in 3G licensee Cyber Access Communications for a cash consideration of...
Link
by rooymans
The proposed agreement is for an eight-year period.
Link
by rooymans
Hong Kong conglomerate Hutchison Whampoa's Irish mobile subsidiary, 3 Ireland, has announced it has 72% UMTS coverage of the population in the country. The operator will also meet the regulator's stipulation in its 3G licence that it cover 85% of the population by the end of 2007. ...
Link
by rooymans
Wie das Nachrichtenmagazin "Profil" in seiner aktuewllen Ausgabe berichtet, wird tele.ring-Chef Michael Krammer zum deutschen Mobilnetzbetreiber E-Plus wechseln. Der Vertrag soll vor wenigen Tagen unterzeichnet worden sein. Krammer wird dort die Nachfolge des mit Jahresende ausgeschiedenen Vorstandschefs Uwe Bergmann ?bernehmen.
?bernahme
Als Datum f?r seinen Amtsantritt wurde der 1. M?rz
This discussion is closed to new replies.
Sort by Trending