What are some Problem solving techniques that can be used in testing. For example I need to think of all the test ideas to test a module ..administrator module for instance.

How can I improve test coverage with using creative methods.

  • Generally I focus on testing all assumptions and play with 'What If' scenarios. Dec 16, 2017 at 10:20

3 Answers 3

  • Use personas such as happy, inpatient, forgetful, angry
  • Use situations such as happy, sad, additional options
  • Use different types of devices to look at the same content
  • Use differently sized devices
  • Test every link
  • Think about what actions you might want to be able to undo
  • Test incorrect input data types
  • Test incorrect numbers, below minimum or above maximum
  • Test using boundary values
  • Test for usability, and w3c / section 508 guidelines
  • Test for feedback that relies solely on color
  • Test for error feedback that is context sensitive and descriptive
  • Test Dates for validity and format

Think up who will use the offered functionality.

What are the tasks of such a person? What are the main priorities that have to be safeguarded?

Crawl into the role. BE the role. Think up hideous happenings that make life hard for your chosen part. Newspaper headings and expert blogs can inspire you there. Risk management input should help as well.

Throw in a bit of Murphy effect and you are coming along quite nicely.

Edit : Murphy's law: "Anything that can go wrong, will go wrong."

Reference: https://en.wikipedia.org/wiki/Murphy%27s_law

  • What is murphy effect?
    – test77
    Feb 26, 2016 at 10:14
  • @test77, I've added a reference in the answer.
    – Bookeater
    Feb 26, 2016 at 23:07

Testing in general falls under the Hypothesis Testing facet of problem solving (I think this bit of software should do A given B (and C and D ad nauseam)).

I think you are more asking, "What problem solving techniques map to software testing."

Divide and conquer - Break each step in the workflow into pieces and validate each piece of action. (To get from A to D, make sure that A to B, B to C, and C to D each work)

Means-ends Analysis - How does each step offer a different way to get to the same solution (or to a dead end). (A to B to C to D works fine, but A to B to G doesn't let me map back to D in any way)

Research - Are there similar things that already exist in your software or similar software.

Trial and Error - Good old exploratory testing.

Personally I've always leaned towards identifying variables, grouping them into like things to limit scope, and using that to define my overall set of conditions and then growing test cases to fit. (matrix style testing)

  • "(I think this bit of software should do A given B (and C and D ad nauseam))" Please can you explain that a bit more.
    – ilm
    Feb 26, 2016 at 2:59

Not the answer you're looking for? Browse other questions tagged or ask your own question.