Showing posts with label software testing. Show all posts
Showing posts with label software testing. Show all posts

Tuesday, December 10, 2013

Rocky Nook book: Improving the Test Process – Implementing Improvement and Change - A Study Guide for the ISTQB Expert Level Module

Improving the Test Process:
This book covers the syllabus for the Improving the Test Process module of the International Software Testing Qualifications Board (ISTQB) Expert Level exam.

To obtain certification as a professional tester at the Expert Level, candidates may choose to take a course given by an ISTQB accredited training provider and then sit for the exam. Experience shows that many candidates who choose this path still require a reference book that covers the course. There are also many IT professionals who choose self-study as the most appropriate route toward certification.

This book can be used both as a preparation guide for those planning to take the ISTQB Expert Level certification exam and as a practical guide for experienced testing professionals who want to develop their skills in improving test processes.

Wednesday, December 4, 2013

last night's online e-book purchases through o'Reilly Media

  • PacktPub--Instant_Nokogiri.20130826122153.pdf (ruby xml)
  • TidBITS--Take_Control_of_Your_Online_Privacy.20130827161623.pdf
  • nostarch--Book_of_GIMP.20130128094115.pdf
  • nostarch--Perl_One_Liners.20131101112448.pdf (perl)
  • rockynook--Testing_Cloud_Services.20130826101828.pdf (testing)


Friday, May 31, 2013

software design paradigm "convention over configuration" applied in software testing

Convention over configuration - Wikipedia, the free encyclopedia

I created a testing framework for one of my projects, and for quite a while I maintained the test cases in a "configuration data structure" (luckily) with rather strict conventions. Let me call that a CDS!
I listed every single test case with all its necessary details there. That was rather cumbersome and did not make me eager to introduce new test cases.
Looking at the fact, that it cost me less than 20 hours to "cast the conventions into code", makes it look rather unclear, why I had hesitated for a couple of months to do so.
Now I am able to drop any "productional data case" into my repository of test cases, and start from there with test driver. That is quiet a relief.

The difference between a raw test case taken from a production system and a (complete) test case executed by my testing framework is "reference data". My testing framework is in a way supportive resp. smart enough by helping in creating "reference data" from the corresponding test data. Certainly a human being must consider the crucial difference between test data and reference data and has to adapt the reference data accordingly.

To be continued.

Wednesday, February 27, 2013

The Pragmatic Bookshelf: Explore It! Reduce Risk and Increase Confidence with Exploratory Testing

Explore It!:
Uncover surprises, risks, and potentially serious bugs with exploratory testing. Rather than designing all tests in advance, explorers design and execute small, rapid experiments, using what they learned from the last little experiment to inform the next. Learn essential skills of a master explorer, including how to analyze software to discover key points of vulnerability, how to design experiments on the fly, how to hone your observation skills, and how to focus your efforts.

Monday, November 19, 2012

O'Reilly Media book: Testing in Scala

Testing in Scala:
Testing in Scala starts with an introduction of the Scala programming language, explains why project infrastructure is critical, and provides compelling reasons to use Scala testing frameworks to not only test Scala code, but Java code too. This book introduces and explains the Simple Build Tool, the Scala answer to Ant, Maven, Gradle, and Buildr. It then explains in detail all the best tools for testing Scala and Java code today--ScalaTest, Specs2, ScalaCheck, and Borachio. Testing in Scala also gives insight on how to integrate coverage tools, continuous integration, web acceptance frameworks, and Java testing frameworks that you already know and love.

Wednesday, November 7, 2012

TestAnything.org :TAP::Parser Cookbook

the cookbook

2013-02-05: The website is up again, but I can't get hold on the cookbook.

2012-11-19: When I tried to look a little around on TestAnything.org in November 2012, the web-site was rather broken. I looked the domain name up on whois.net, found Andy Armstrong and his e-mail address, and dropped him a note. This is how the error message looked like:

Test Anything Protocol has a problem
Sorry! This site is experiencing technical difficulties.
Try waiting a few minutes and reloading.
(Can't contact the database server: Unknown database 'testanything' (localhost))

TAP = Test Anything Protocol - Wikipedia, the free encyclopedia

Test Anything Protocol - Wikipedia, the free encyclopedia

Monday, November 5, 2012

CPAN: Test::Tutorial - A tutorial about writing really basic tests

Test::Tutorial - A tutorial about writing really basic tests - metacpan.org

I wrote some code to test a customer's perl code, not having (had) a look at Test::More or whatever beforehand.
After completing my task, I tweaked my code to make use of Test::More. Now it's optionally creating TAP.
My next step: reading and exercising.

Wednesday, September 26, 2012

chromatic's book "Modern Perl"

Q: Where to download from? A: [Link]

Table of Contents

  • Unicode and Strings [Link]
  • Moose [Link]
  • Testing [Link]
  • POD [Link]
  • transforming a main program into a module, so that we can test also it local subroutines separately [handling main], [controlled execution] –– I call this "main à la Python"

O'Reilly Media book: Advanced Perl Programming, 2nd Edition

Advanced Perl Programming, 2nd Edition - O'Reilly Media


Just put the 1st paperback edition on top of the batch going to the charitable book collection.

From the TOC:

  • Chapter 8: Testing; with a subchapter on "Keeping Tests and Code Together" within POD sections of the source code

Monday, September 24, 2012

O'Reilly Media book: Perl Testing: A Developer's Notebook


Perl Testing: A Developer's Notebook - O'Reilly Media

Is there any sexier topic in software development than software testing? That is, besides game programming, 3D graphics, audio, high-performance clustering, cool websites, et cetera? Okay, so software testing is low on the list. And that's unfortunate, because good software testing can increase your productivity, improve your designs, raise your quality, ease your maintenance burdens, and help to satisfy your customers, coworkers, and managers. […]

In chapter 7 ("Testing Web Sites") the book has a rather nice example on recording a web-surfing session, that creates a perl script to replay that session: "Record and Play Back Browsing Sessions". But  they say, there is trouble with HTTP::Recorder as of the time of writing of that book – and it still does not really work for me. How bad. Nice but unusable.

chromatic in "Modern Perl" on Testing

Managing Real Programs (Modern Perl 2011-2012)

Thursday, August 2, 2012

O'Reilly Media book: Intermediate Perl, 2nd Edition

Intermediate Perl:
Get a clear roadmap for improving your skills with Intermediate Perl, and gain working knowledge of Perl's objects, references, and modules—ingredients that make the language so versatile and effective. Written by the authors of the bestselling Llama book, Learning Perl, and updated for Perl 5.14, this book offers a gentle but thorough introduction to intermediate programming in Perl.

  • Chapters 14 and 20: testing
  • Chapter 12: Creating Your Own Perl Distribution; has a section on "Plain Ol’ Documentation" (POD)
  • Chapter 19: Moose
  • Chapter 13 and 15: OO