Error message

  • Notice: Undefined offset: 221 in user_node_load() (line 3642 of /home/www-data/ukalf/wwwroot/modules/user/user.module).
  • Notice: Trying to get property of non-object in user_node_load() (line 3642 of /home/www-data/ukalf/wwwroot/modules/user/user.module).
  • Notice: Undefined offset: 221 in user_node_load() (line 3643 of /home/www-data/ukalf/wwwroot/modules/user/user.module).
  • Notice: Trying to get property of non-object in user_node_load() (line 3643 of /home/www-data/ukalf/wwwroot/modules/user/user.module).
  • Notice: Undefined offset: 221 in user_node_load() (line 3644 of /home/www-data/ukalf/wwwroot/modules/user/user.module).
  • Notice: Trying to get property of non-object in user_node_load() (line 3644 of /home/www-data/ukalf/wwwroot/modules/user/user.module).
  • Notice: Undefined offset: 66 in user_node_load() (line 3642 of /home/www-data/ukalf/wwwroot/modules/user/user.module).
  • Notice: Trying to get property of non-object in user_node_load() (line 3642 of /home/www-data/ukalf/wwwroot/modules/user/user.module).
  • Notice: Undefined offset: 66 in user_node_load() (line 3643 of /home/www-data/ukalf/wwwroot/modules/user/user.module).
  • Notice: Trying to get property of non-object in user_node_load() (line 3643 of /home/www-data/ukalf/wwwroot/modules/user/user.module).
  • Notice: Undefined offset: 66 in user_node_load() (line 3644 of /home/www-data/ukalf/wwwroot/modules/user/user.module).
  • Notice: Trying to get property of non-object in user_node_load() (line 3644 of /home/www-data/ukalf/wwwroot/modules/user/user.module).
  • Notice: Undefined offset: 66 in user_node_load() (line 3642 of /home/www-data/ukalf/wwwroot/modules/user/user.module).
  • Notice: Trying to get property of non-object in user_node_load() (line 3642 of /home/www-data/ukalf/wwwroot/modules/user/user.module).
  • Notice: Undefined offset: 66 in user_node_load() (line 3643 of /home/www-data/ukalf/wwwroot/modules/user/user.module).
  • Notice: Trying to get property of non-object in user_node_load() (line 3643 of /home/www-data/ukalf/wwwroot/modules/user/user.module).
  • Notice: Undefined offset: 66 in user_node_load() (line 3644 of /home/www-data/ukalf/wwwroot/modules/user/user.module).
  • Notice: Trying to get property of non-object in user_node_load() (line 3644 of /home/www-data/ukalf/wwwroot/modules/user/user.module).

Blogs on this site

Mentoring (Insane developers)

I was approached at a conference by a test manager who told me that:

  • A supplier was refusing to resolve a defect.
  • The supplier complained they could not reproduce the defect.
  • The supplier was not prepared to come in and see the defect for themselves.
  • The contract was either unenforceable, or protected by "special relations" between her management and the supplier.
  • Her management was blaming her for the problem.

    I told her that she should:

  • write a brief paper describing the problem.
  • record the defect using a screenscrape programme.
  • Dogma v's Reality: Reality always wins

    It never ceases to amaze me how people get caught up in the dogma of methodologies; how you must do X as that is what is in the book. This is particularly amusing when you hear people saying you must do X to be Agile. I cannot but think they have missed the point; being Agile requires you to be flexible in your dogma not dogmatic in your flexibility.

    Testing Tags: 

    Muckup Time

    I was meeting some friends last night before going to a concert and was reflecting as I was enjoying a pint waiting for the others to arrive. I was, as usual, early because I had included mucking up time in my plans and nothing had mucked up. I say mucked up to spare the blushes, rather than the less polite expression I would generally use.

    I include mucking up time in my plans because I like to have contingency as I'm human and make mistakes; get distracted; meet people; take longer to finish the previous task; have a conversation; etc.etc.etc.

    Muckup Time

    I was meeting some friends last night before going to a concert and was reflecting as I was enjoying a pint waiting for the others to arrive. I was, as usual, early because I had included mucking up time in my plans and nothing had mucked up, I say mucked up rather than the less polite expression I would generally use to spare the blushes.
    I include mucking up time in my plans because I like to have contingency as I'm human and make mistakes; get distracted; meet people; take longer to finish the previous task; have a conversation; etc. etc.etc.

    Reflections on the state of our industry

    I have been reflecting on the ethical standards in our industry, not those of sales and marketing but those of development teams serving business. What prompted this was hearing someone celebrate success last week when they were talking about a product that required emergency fixes in the first week in live and was riddled with errors and poor design.

    "Test Driven Development” or “Requirements Driven Development"?

    The term “Test Driven Development” appears far more widely than the term “Requirements Driven Development”. However, I argue that it is the latter which should often be the driving force. That is, unless the project is extremely agile and requirements only emerge through trial and error. T.D.D. seems to be a great approach to unit testing, but for the higher level test phases I argue that we should be looking to elaborate test cases through the exploration of requirements and it is the linkage between successful tests and requirements which ultimately prove the worth of the development.

    My first blog: Random thoughts.

    Yesterday I attended the Test Managers Forum in London; and was suitably shamed into attempting to give back a little and use the Blog that is supplied when registering with TMF. I apologise if your reading this as the last thing I've blogged; and it's 2012. I never was good at keeping a diary and terrible at writing papers. Could be why I took the practical route to the industry and not the academic. I couldn't face having to write a 1000 page thesis on holography in a two dimensional broadcasting world.

    UK Testers Forum – quarterly meeting – 27/10/2010

    The discussions I attended shared a common theme:
    This was that the focus of testing needs to be on business goals rather than narrow requirements. The best requirements are those that have examples or tell a business story. However, we do need robust stories – throwaway stories do not serve this purpose.
    When documenting our tests we can then keep in step with these examples along with our test data.

    Test Automation tools and Frameworks. What are the recent trends?

    We are using HP Quality Center for our test management tool, and all of our manual tests are created and executed in this. For test automation our vendor test specialists use QTP with a proprietary framework, that integrates with Quality Center.

    1 Manual test creation productivity is 10 tests/person/day.
    2.Automated test creation productivity is 1 test / person / day, using QTP with the framework. Is this a reasonable productivity level? - What would you expect it to be?
    3.Are there any open source frameworks that could be used with QTP and QC to improve productivity?

    Pages