Saturday 6 September 2008

Testing

When we software engineers do a live functional test of a system -as you have to do from time to time- then there are two options.
  1. Do the test at a time that causes least disruption to users of the product. Based on your system's known use pattern, you schedule the operation for a quiet time -like a Sunday morning. If the test works, few people notice. If things go wrong, well, damage is minimal and you have the rest of the day to roll back. The main inconvenience here is to the development team, who get phone calls from the operations team once -not if- the system fails.
  2. Do it during working hours when it is most convenient to the development team. This is best for the developers, but generally worse for end users, more of whom discover the system is down
You can determine what philosophy a team is operating on by when they run their functional tests on the live system.

(photo taken in central Bristol on Friday afternoon, 2:04pm)

at

No comments:

Post a Comment

Commenters MUST NOT post spam, MUST NOT post requests for cross linking and MUST NOT post up requests for paid links. Such attempts SHALL result in one or more postings in which we MAY be rude or we MAY make fun of you and MAY include your public email address. Furthermore, we MAY report you to google for attempts at paid linking, who SHALL then punish your site.

Comments are closed after two days -after that they are moderated. You MUST be logged in to post.

This statement follows RFC2119 rules regarding the use of MUST, MUST NOT, MAY, and SHALL and MUST be treated as normative.