If one was to look at my Thunderbird client, they would see a very big number beside the agile-testing list. In fact, I haven’t really processed it since the third week of January it would seem. I was going to go to the baseball game tonight, but it ended up being an afternoon game so I didn’t go and since I’m in Atlanta with nothing better to do, a processing I go…

  • Four definitions of ‘designed for testability’:
    1. Designed for automated, unattended evaluation
    2. Breaking down the app so it can be tested as a series of logical chunks
    3. Scaffolding
    4. Places logs and write timing information to them
  • ‘Planning for testability’ is just as, if not more important, than ‘design for testability’
  • PNSQC paper by Bret Pettichord about designing for testability
  • If you need it and know how, do it. If you need it and don’t know how, learn how and do it. If you don’t need it, don’t do it. – Ron Jeffries
  • Panopticode – cool visualization tool for things like code coverage
  • Sonar – Sonar enables you to collect, analyze and report metrics on source code. Sonar not only offers consolidated reporting on and across projects throughout time, but it becomes the central place to manage code quality
  • For entry level automaters doing Siebel work, Mercury’s Quick Test Pro may be a good starting point. QTP uses VBScript, so you won’t be able to reap the benefits of an OO language as the team gets better (and they can be huge benefits), but QTP has a huge advantage in the market – they have a contract with Oracle to provide libraries that recognize the screen objects for Oracle’s applications. I’m fairly certain QTP has Siebel libraries, but you should doublecheck. But it may not be as friendly to the backend systems (how do you verify the input to Siebel propagated properly to the integrated systems and vice-versa? The question to ask is – Can QTP automate that?)
  • Use in-memory databases for unit tests
  • Understanding and Solving Internet Explorer Leak Patterns
  • One of my colleagues brought up the best definition for “seniority” I’ve ever heard. It’s not age, or tenure, or experience. It’s “When I don’t have to worry about you”. – Rachel Blum
  • Rumbster is a simple SMTP server that receives email sent from a SMTP client. Received emails are published to observers that have registered with Rumbster. There are currently two observers; FileMailObserver and MailMessageObserver.
  • Dumbster – the Java version of the above
  • and a .NET version
  • Methodologies fit the context
  • TOMOS – TOMOS improves communication and collaboration between business analysts, developers, testers and managers.
  • Break “large refactorings” down into a series of small ones, with the tests passing after each one. Not only is this to be safer, but also faster.

Hmmm. Thought that this would be much longer. Some useful things though.