Many Pies

Many Pies

Tuesday, June 28, 2022

Users as testers

Photo by Michael Dziedzic on Unsplash

By "Users as testers" I don't mean the way some companies throw out software which isn't quite finished, without admitting that, and let people find the bugs.

I'm talking about normal human beings, as opposed to IT people, who get to use technology that previously would have been unavailable or require too much specialist skill. This article is for you normal human beings, and says what you need to know about testing stuff.

Thinks break by themselves

I remember someone who had set up some sort of automatic process and was surprised when it stopped working, without them realising. He said, "I assumed that once it was set up it would keep on working". It would be really nice if that was the case, but unfortunately it's not. The trouble is with processes like this, like something that sends you an email if some rare event happens
  • something somewhere along the line gets changed and things don't fit together and they stop working
  • something was a paid service and someone stopped paying the bill, or a credit card expires and no-one notices
  • a computer gets upgraded and the thing is no longer possible with the upgraded system
  • someone leaves, their email gets closed down, and then no-one gets notified

So if a process is important to you, then it's worth checking regularly that it works. How regularly? Ask yourself how soon would you like to know that it stopped working.

If you change something then you have to check it

Many years ago I was working on a system for controlling gas pipelines. Something asked me to make a very small change. I didn't check that the change worked, as they were in a hurry. They took the tape the next day (it was many, many years ago) and went to the control room and installed the new version. It didn't work, so their whole day was wasted.

Even if you're not a programmer you might:
  • write a spreadsheet formula
  • create a form
  • use some fancy website tool which links two things together
If you change something then you have to check that it works. The thing you change might be something as simple as adding a new thing to a list. There are several ways that just adding the thing may not work out:
  • There are in fact two lists, and you need to add the new thing to the other list too
  • You may have typed something in that's too long, and it doesn't work
  • There are a maximum of five items in the list and you just added the sixth
So if you change something, then check that whatever you changed has the effect that you want.

The other check

The other thing to check is that everything else works as it should before. As I said above, just because something was working doesn't mean it will carry on. In making a change in one area something else may now not work, as a side effect of what you've just done. It's not going to be practical to check every aspect, but you can check two things:
  1. If you have an idea how things work underneath (and you may not, some things are very mysterious) then you can check the things that are linked to what you changed.
  2. The important things - do they still work?

How to check

I can't give much specific advice on this, because a lot depends on whatever it is you're changing. Here are some general tips though:
  • Check things two ways, such as adding up numbers from two different sources that should be the same
  • Assume you know nothing about how it works (which may be true - see "mysterious" above), check that it does what it should be doing
  • Check the extremes - the biggest or smallest numbers
  • Put in rubbish - if a number is expected then how does it handle ?Elephant99!
  • Try different combinations. If you have something that can be A or B and something else that can be X or Y then try AX, AY, BX and BY in case there's some interlink

Tuesday, July 06, 2021

From Causeview to NPSP

It's been a while since I said anything about Salesforce on here. I'm now able to talk about something that's been going on for a while. For the past four years we've been using Causeview (recently acquired by Softerware, the company behind DonorPerfect) for donations processing and events. We've decided to switch to NPSP. It was available at the time we switched to Salesforce from Raiser's Edge, but is looking a better product these days.

It's not a like for like switch, as Causeview includes Gift Aid and Direct Debit handling, which NPSP doesn't, so we're using Findock for those parts.

So far, so executive summary. We're right in the messy middle of the project, with dataloading going on now ready for UAT soon. So there's lot's going on.


Friday, October 25, 2019

Downloading Yahoo Groups emails (and other stuff)

Yahoo is closing its groups website. The email function will still work, but there will be no web presence.

Attention: Starting December 14, 2019 Yahoo Groups will no longer host user created content on its sites. New content can no longer be uploaded after October 28, 2019. Sending/Receiving email functionality is not going away, you can continue to communicate via any email client with your group members.

Recently I downloaded the emails, pictures and files from a group. I found a Python script to do it. I couldn't get it to work with my username and password, even though I generated an application specific password for it. I did get it to work like this though:

  • Log into Yahoo and join the group if you haven't already (if it's a public group you may not need to join it.
  • In Chrome press F12, go to Application Tab, Cookies under Storage and click on https://groups.yahoo.com
  • Find the line with T in the Name column
  • Right click on the Value column and choose edit
  • Copy the long string and paste it somewhere
  • Repeat for the Y cookie.
  • Edit the file yahoo.py and put the T and Y values into this line:
yga = YahooGroupsAPI(args.group, "T value", "Y value")

Run the script (I'm assuming you know how to do that), and you should find it downloading all emails, files and attachments.

You end up with .eml files for each email. In order to get them into something vaguely readable I used Thunderbird, imported all the eml files into a local folder, and then used the ImportExportTools addon in order to export the folder. You end up with an index.html file with a link to html emails in a subdirectory.

It would be nice if the index file had a threaded view, but that doesn't seem to be in the addon.

Tuesday, October 08, 2019

Ada Lovelace Day 2019 - Julia Evans

For this year's post I'm writing about Julia Evans. She makes really well produced zines about programming - so Linux, HTTP, networking etc. She's gone full-time to do this and recently she posted about the revenue she gets from it, which is useful, because I rarely see how much people make from side-projects and former side-projects.

Tuesday, October 09, 2018

Ada Lovelace Day 2018 - Dr Hannah Fry

I've not done posts for Ada Lovelace Day since 2015, for no good reason I can think of. This year I'm highlighting Dr Hannah Fry.

Her book, Hello World, was released recently, so she's quite active on Twitter at the moment promoting that.


I've picked her because she's a good broadcaster and explainer of maths. I particularly enjoy the Curious Cases of Rutherford & Fry, a 10 minute radio programme where they answer questions put by listeners. Each episode seems much longer as they pack so much in. The podcast version is a lot longer, so worth listening to in preference to the radio show.

You can see a list of other programmes she's done on her media page. I've enjoyed all of those that I've seen. This is my favourite tweet she's done (because I get the joke):


My previous Ada Lovelace Day posts are here.


Thursday, September 13, 2018

Work for me!

We're advertising a Business Systems Assistant job to help share my workload. If you've come here after being there, then full marks for doing your homework. Mention this blog post should you be called to interview and you may get bonus points.

If you think that a Macbook is standard issue, then I'm afraid you're going to be disappointed. That's stock photography for you. I don't much talk about what I do here, because it's mostly behind the firewall. However, with moving to Salesforce and launching a website (within a couple of days of each other) last year, and with moving to SunSystems and Workday later this year, and next year, there's a lot of work to be done. Plus we're doing a lot more in terms of fundraising, which means that people are hungry for data. So I've got enough work for two people, which is why we need another one!

Tuesday, June 26, 2018

Morriss' law(s)

I recently came across a couple of lists of software development laws:
The eponymous laws of software development
Laws of software development

I may or may not have publicly stated Morriss' law:
Every site/program/app attempts to expand until it resembles Twitter
See Facebook, Skype, Confluence

However on one of those lists I cam across:

Zawinski’s Law

This law addresses software bloat and states…
Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.


I was going to state Morriss' second law, which is like the first one, but has "until it has Stories", but I think there's Morriss' greater law at work here, which is something like:

If they copy you, you're doing something right.
 There's probably a better way of saying it though.