London software testing news UK

Test Driven Development

Posted in Acceptance testing by testing in London on November 14, 2011

If you want to know about “Test Driven Development for Robots” then you could try attending the next meeting of the BCS SPA on Tuesday 6th Dec 2011 at BCS Davidson Building, 5 Southampton Street, London WC2E 7HA

“They followed a test-driven development (TDD) approach for C++ using CppUTest, as described by James Grenning, to create a state machine to turn sensor readings into motor control instructions (with hindsight, we might have saved time by resorting to the Machine Objects library). Once this was working, it was linked with an application developed for an Android tablet computer that could be used to instruct the robot to go to any selected station, pick up/drop a “payload” (only conceptually) and return to base.”

For more information visit: http//

London Games Testing Events

Posted in Acceptance testing by testing in London on November 2, 2011

The London 2012 sports testing programme, the London Prepares series, continues next year.

The London Prepares series enables LOCOG to test key aspects of their operations ahead of next year’s Games – such as results, scoring and timing systems, the fields of play, the venues and the people who will be working to ensure the Games run smoothly.

Tickets for the next events will go on sale at 10am on 17 November 2011 via Ticketmaster – giving you a great chance to be among the first to experience world-class sporting action at a London 2012 venue.

Acceptance test RFP

Posted in Acceptance testing,Software testing by testing in London on October 31, 2011

This is from a public RFP issued in October. It gives an idea of how important acceptance testing is to some contracts:

“…requires four types of acceptance tests: functional, performance, reliability and availability. The Proposed Acceptance Test Plan (ATP) should address all four types of acceptance tests.

Acceptance tests will be conducted first on each System Component (e.g., CAD, Mobile, LRMS, Field Reporting and FRMS) independently. Upon acceptance of all System Components, a final set of Functional, Performance and Reliability Acceptance Tests will be performed on the integrated System to ensure that all Components work together as intended and at the contracted performance levels. The County will notify the Proposer of the successful completion of each test in accordance with task completion requirements in the Statement of Work.

In the event a Level 1 Error is corrected by the Proposer, then subsequently fails on two (2) additional occasions within the test period, the County has the right to be refunded all previous payments under the Contract.”

IEEE Acceptance testing

Posted in Acceptance testing,Software testing by testing in London on October 26, 2011

I found this beta vesion  of the IEEE Technology Navigator yesterday. The page I found was on Acceptance Testing and it identified  1.785 reosurces for acceptnace testing. That seems a lot of resouces. That is until you compare it with the 284K  resouces related to the more general topic of testing.

Amongst the resources are the following standards:

  •  IEEE Guide: Test Procedures for Synchronous Machines Part I– Acceptance and Performance Testing Part II-Test Procedures and Parameter Determination for Dynamic Analysis
  • IEEE Recommended Practice for Field Testing Electric Submersible Pump Cable
  • IEEE Recommended Practice for Testing Electronics Transformers and Inductors
  • IEEE Standard Conformance Test Procedures for Equipment Interconnecting Distributed Resources with Electric Power Systems
  • IEEE Standard for Software and System Test Documentation

Overview of IEEE 829-2008

Acceptance testing

Posted in Acceptance testing by testing in London on October 25, 2011

Recently saw this statement about acceptance testing: “Acceptance testing is not about bug hunting or ‘breaking’ the software; it is about testing your requirements in real life conditions.”. It came from a large company that supplies testing and IT services.

Agree or disagree? What if we made it more general “testing is not about bug hunting or ‘breaking’ the software; it is about testing your requirements in real life conditions.“. Now what do you think?

You’ve probably heard this statement many times in various forms. Does shifting emphasis from a negative concept (finding mistakes) to a positive concept (showing that the requirements have been met) make testing more acceptable? Possibly. What it definitely does is move the focus from detecting things that aren’t working to declaring that things work. And this will affect how the acceptance testing team behaves.  There are few better ways to discourage bug detection than stating that this is definitely not what testing is about.

Testing should always be about finding bugs and as soon as we change that motivation we lower the effectiveness of the testing we perform.

Software testing with Visual Studio

Posted in Acceptance testing by testing in London on October 21, 2011

There is a book review here on software testing with Visual Studio. The view of the reviewer is that the book provides a good overview of testing with Visual Studio but that there are a lot of topics omitted. For example he mentions that it doesn’t cover stress testing, fuzzing and load testing. However, on the whole the review, which outlines what is in each chapter of the testing book,  is positive.

If you’re interested in getting a copy its Software Testing with Visual Stuio 2010 by Jeff Levinson & Steven Borg; published by Addison-Wesley, ISBN: 978-0321734488.

Vizual Studio Load Testing

Open Source test tool downloads

Posted in Acceptance testing by testing in London on May 27, 2011

What testing tool has now passed teh 10,000 download mark? It’s an open source test tool. Its for testing mobile applications and web apps. It’s particularly good at testing Adobe Flex. Still not sure. No still not got it. Well, its a test tool from a thinking primate.

Yes that’s right! Gorrila Logic have annouced that there have been over 10,0000 downloads of FlexMonkey – their open source testing tool.

FlexMonkey allows developers and testers of rich Internet applications to record, playback and verify real-world user interactions. If desired, the test automation tool can also generate ActionScript test scripts that teams can easily use within a continuous integration environment. “

Acceptance criteria

Posted in Acceptance testing by testing in London on April 29, 2011

This extract is from Chapter 25 of a book that I found online. This chapter deals with acceptance testing in fact it starts by advising that acceptance testing should be like voting – do it early and do it often. I t then goes on to the role of eductating the customer on acceptance testing. The extract below is from the passage on acceptance criteria:

Remind the customer that she defined acceptance criteria in the acceptance tests. Anything that causes an acceptance criterion not to be met is a defect. This is why you invest time in making sure the acceptance tests are thorough and that the development team has clearly understood the customer’s requirements. The customer needs to understand that in spite of the best efforts and best XP practices of the team, some defects will probably be discovered by acceptance tests, andafew may even make it past both the unit and acceptance tests. Explain the options available for handling these defects.

IEEE unveil three testing standards for the Super Grid

Posted in Acceptance testing by testing in London on April 27, 2011

IEEE (Institute of Electrical and Electronics Engineers) is developing technical standards to assure an improvement in the performance of fibre optic elements in teh Smart Grid.

The “Standard for Testing and Performance of Hardware for Optical Groundwire (OPGW) ” covers the procedures & processes for construction and performance of hardware used with OPGW cables. It also includes the  testing requirements and the acceptance criteria to be used in acceptance testing hardware.

The “Standard for Testing and Performance of Hardware for All-Dielectric Self-Supporting (ADSS) Fiber Optic Cable” aims to simplify how product quality assurance and testing are performed to help procurement of ADSS systems.

 Finally “Standard for Qualifying Hardware for Helically-Applied Fiber Optic Cable Systems (WRAP Cable)” covers performance, testing requirements and the acceptance criteria for the acceptance test of WRAP ccable used in the Super Grid.

The QA phase of better website development

Posted in Acceptance testing,Software testing by testing in London on April 22, 2011

From Zdnet

The testing phase of the methodology is intended to capture and resolve any issues, bugs or problems. If there is one overlooked aspect of website development, it is typically in the testing process. There are two stages of testing:

  • System Acceptance Testing – Using internal resources, begin the system testing phase by documenting specific test cases created using the business and functional requirements obtained during the Discovery Phase.
  • User Acceptance Testing – The final phase of activity before deployment is to conduct user acceptance testing. With the previous testing phase, you used IT developers and QA staff to do the testing and issue resolution activities. In this phase, you will use actual end-users to validate the site experience.
Next Page »