Welcome to the new Agile Record!

You might have wondered what the meaning behind the “Big changes coming” banner on the Agile Record home page was.

The new format of Agile Record magazine

Agile Record will still be the same magazine, but now in a new format: We switch from PDF download to blog format. Why? We want to place emphasis on conversation. Many of you have told us: I have learned a lot reading Agile Record, but I’d like to discuss this article with my peers. What if you could conveniently share your opinion and learn more through conversation with other professionals? That was our incentive to create the Agile Record blog and we would like you to join us in this project!

What are the advantages of the new Agile Record?

  • The new format provides more visibility for authors, who have always been the heart and soul of this magazine. The conversation starts with their articles!
  • All information is now accessible for you from any device, 24 hours a day, without any downloads.
  • You now have a space to talk about the Agile Record topics with your peers. You can easily share and comment on articles via various social media sites.

What changes for you?

In essence, Agile Record is still the same magazine as before, but with a few cimprovements:

For our writers:

  • The magazine will suggest a topic every 3 months, just like before.
  • If you are interested in becoming a contributor and writing an article, you submit your article to our online system. It will then be reviewed by our editorial board and you will be informed about the next steps.
  • Instead of releasing all the articles at once, articles will be published during the three-month period until the new topic begins.
  • So, if you have already written an article for Agile Record you will see: the publishing process and deadlines don’t change at all, only the release date of the articles.

For our readers:

  • You will have new content to read on a regular basis, all in small bites.
  • Soon a rating system will be established directly on the blog!
  • Share your favorite articles with your friends and co-workers and comment on various social media platforms.
Twitter Agile Record Google+ Community Agile Record Facebook Agile Record
    • be notified as soon as a new article is released on Agile Record!
    • receive a newsletter with all articles related to the current topic once this topic cycle is finished. You will have them sorted by topic and will be able to create your own Agile library!

And last, but not least …

Where can I get previous issues of Agile Record?

The Agile Record team is working hard to convert the content from PDF to blog entry. We have already converted two issues:

In the meantime you can download the PDF versions of the latest issues on our Download Page.

In conclusion: with the relaunch of Agile Record we are creating a new space for discussion and resources to hopefully help you with your daily work.


José Díaz

José Díaz is the CEO of Díaz & Hilterscheid GmbH and Chief Editor of the Testing Experience, Testing Experience DE and Agile Record magazines. He organizes the annual Agile Testing Days, Agile Dev Practices and Mobile App Europe. He began...
Read more about José Díaz

2 Comments. Leave new

Ahmad Al-hamed
Mai 23, 2014 7:31 pm

I strongly support publishing the topics on the blog for discussion purposes. However, I also strongly support keeping the PDF version since we need to keep them as references for the future. I will appreciate if you think again in the PDF version with keeping the blog idea.

Thank you

Hi Dave, Great article you’re right that on the DBA side we soimetmes miss out on the cool stuff such as NUnit. TSQLUnit is pretty cool for getting started with T-SQL unit testing. You might also want to take a look at tSQLt (www.tsqlt.org). One of the problems I kept running into with writing T-SQL unit tests was this: Suppose I have a table that is referenced by 5 views, and I need to write about 5 test cases per view to feel like I’ve really covered the functionality. This means, I have about 25 test cases for these views that insert data into that table. If I later need to add a constraint to that that table, or a non-nullable column, or similar change even if it doesn’t have anything to do with the views I am testing my test cases are likely to all break. That’s a lot of extra maintenance as you grow your test suite. tSQLt was written to handle these problems specifically. It has features, such as FakeTable and SpyProcedure which behave a little bit like the mocking frameworks found in other unit testing platforms for OO code.Anyway, it’s always encouraging to see more people getting involved in unit testing their SQL code!

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht.