Whether or not to use old test data

This week I read a great blog on starting from scratch or
using old test documentation. The writer formed the blog based on a question
asked by one of his fellow testers, “How can I find old test documentation for
a completed feature so I can re-use those test on a similar new feature?”.
My initial thought was that’s actually not a bad idea, but
the more I read the more I was swayed and started thinking about times when I
was either asked about a similar situation or posed the same question. Though I
wasn’t software testing at the time nor even in the industry this can be
applied to other scenarios as well.
While I do think that it is a good idea to track and refer
to past tests to see what has been done, I agree with the writer that “a
skilled tester can usually come up with better tests…today, from scratch.” He
makes many valid points and I will go over a couple that I thought to me stood
out, you can read the blog to get the rest if you’d like.
  • ·        
    A skilled tester knows more about testing today
    than they did last month.

         How true. The more you do something the
more you learn about it and the better you become at          it.
  • The product-under-test is different today than
    it was last month.  It might have new code, refactored code, more users,
    more data, a different reputation, a different platform, a different time of
    the year, etc.

          As the development process moves through
the different iterations, things change. Looking at             past tests may help, but
more probably than not it will probably slow you down. You have first           locate
the tests that were done and figure out what the tester was thinking if it wasn’t
you, and             then try and decide whether or not it even applies to the new code. By
the time you figure that             stuff out I would imagine you could have written
several test cases according to the latest                     iteration.

  • The test environment might be different.

          This is true as well, things seemingly change
frequently so you may have changed the                         environment and once again wasting time
seeing what you or someone else did.

The bottom line here is that while in some cases the old
data may help, but more than likely it will, in my opinion slow you down. One
more thing I think can happen is can stagnate your thought process as you are
looking at old ideas instead of coming up with new ideas.
http://www.testthisblog.com/2016/03/start-from-scratch-vs-old-test.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.testthisblog.com/2016/03/couple-automated-checks-with-product.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.testthisblog.com/2016/02/automated-checking-is-very-human.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.softwaretestingmagazine.com/knowledge/how-to-give-better-code-reviews/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+SoftwareTestingMagazine+%28Software+Testing+Magazine%29
http://www.developsense.com/blog/2016/05/testers-dont-prevent-problems/

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Whether or not to use old test data

This week I read a great blog on starting from scratch or
using old test documentation. The writer formed the blog based on a question
asked by one of his fellow testers, “How can I find old test documentation for
a completed feature so I can re-use those test on a similar new feature?”.
My initial thought was that’s actually not a bad idea, but
the more I read the more I was swayed and started thinking about times when I
was either asked about a similar situation or posed the same question. Though I
wasn’t software testing at the time nor even in the industry this can be
applied to other scenarios as well.
While I do think that it is a good idea to track and refer
to past tests to see what has been done, I agree with the writer that “a
skilled tester can usually come up with better tests…today, from scratch.” He
makes many valid points and I will go over a couple that I thought to me stood
out, you can read the blog to get the rest if you’d like.
  • ·        
    A skilled tester knows more about testing today
    than they did last month.

         How true. The more you do something the
more you learn about it and the better you become at          it.
  • The product-under-test is different today than
    it was last month.  It might have new code, refactored code, more users,
    more data, a different reputation, a different platform, a different time of
    the year, etc.

          As the development process moves through
the different iterations, things change. Looking at             past tests may help, but
more probably than not it will probably slow you down. You have first           locate
the tests that were done and figure out what the tester was thinking if it wasn’t
you, and             then try and decide whether or not it even applies to the new code. By
the time you figure that             stuff out I would imagine you could have written
several test cases according to the latest                     iteration.

  • The test environment might be different.

          This is true as well, things seemingly change
frequently so you may have changed the                         environment and once again wasting time
seeing what you or someone else did.

The bottom line here is that while in some cases the old
data may help, but more than likely it will, in my opinion slow you down. One
more thing I think can happen is can stagnate your thought process as you are
looking at old ideas instead of coming up with new ideas.
http://www.testthisblog.com/2016/03/start-from-scratch-vs-old-test.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.testthisblog.com/2016/03/couple-automated-checks-with-product.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.testthisblog.com/2016/02/automated-checking-is-very-human.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.softwaretestingmagazine.com/knowledge/how-to-give-better-code-reviews/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+SoftwareTestingMagazine+%28Software+Testing+Magazine%29
http://www.developsense.com/blog/2016/05/testers-dont-prevent-problems/

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Whether or not to use old test data

This week I read a great blog on starting from scratch or
using old test documentation. The writer formed the blog based on a question
asked by one of his fellow testers, “How can I find old test documentation for
a completed feature so I can re-use those test on a similar new feature?”.
My initial thought was that’s actually not a bad idea, but
the more I read the more I was swayed and started thinking about times when I
was either asked about a similar situation or posed the same question. Though I
wasn’t software testing at the time nor even in the industry this can be
applied to other scenarios as well.
While I do think that it is a good idea to track and refer
to past tests to see what has been done, I agree with the writer that “a
skilled tester can usually come up with better tests…today, from scratch.” He
makes many valid points and I will go over a couple that I thought to me stood
out, you can read the blog to get the rest if you’d like.
  • ·        
    A skilled tester knows more about testing today
    than they did last month.

         How true. The more you do something the
more you learn about it and the better you become at          it.
  • The product-under-test is different today than
    it was last month.  It might have new code, refactored code, more users,
    more data, a different reputation, a different platform, a different time of
    the year, etc.

          As the development process moves through
the different iterations, things change. Looking at             past tests may help, but
more probably than not it will probably slow you down. You have first           locate
the tests that were done and figure out what the tester was thinking if it wasn’t
you, and             then try and decide whether or not it even applies to the new code. By
the time you figure that             stuff out I would imagine you could have written
several test cases according to the latest                     iteration.

  • The test environment might be different.

          This is true as well, things seemingly change
frequently so you may have changed the                         environment and once again wasting time
seeing what you or someone else did.

The bottom line here is that while in some cases the old
data may help, but more than likely it will, in my opinion slow you down. One
more thing I think can happen is can stagnate your thought process as you are
looking at old ideas instead of coming up with new ideas.
http://www.testthisblog.com/2016/03/start-from-scratch-vs-old-test.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.testthisblog.com/2016/03/couple-automated-checks-with-product.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.testthisblog.com/2016/02/automated-checking-is-very-human.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.softwaretestingmagazine.com/knowledge/how-to-give-better-code-reviews/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+SoftwareTestingMagazine+%28Software+Testing+Magazine%29
http://www.developsense.com/blog/2016/05/testers-dont-prevent-problems/

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Whether or not to use old test data

This week I read a great blog on starting from scratch or
using old test documentation. The writer formed the blog based on a question
asked by one of his fellow testers, “How can I find old test documentation for
a completed feature so I can re-use those test on a similar new feature?”.
My initial thought was that’s actually not a bad idea, but
the more I read the more I was swayed and started thinking about times when I
was either asked about a similar situation or posed the same question. Though I
wasn’t software testing at the time nor even in the industry this can be
applied to other scenarios as well.
While I do think that it is a good idea to track and refer
to past tests to see what has been done, I agree with the writer that “a
skilled tester can usually come up with better tests…today, from scratch.” He
makes many valid points and I will go over a couple that I thought to me stood
out, you can read the blog to get the rest if you’d like.
  • ·        
    A skilled tester knows more about testing today
    than they did last month.

         How true. The more you do something the
more you learn about it and the better you become at          it.
  • The product-under-test is different today than
    it was last month.  It might have new code, refactored code, more users,
    more data, a different reputation, a different platform, a different time of
    the year, etc.

          As the development process moves through
the different iterations, things change. Looking at             past tests may help, but
more probably than not it will probably slow you down. You have first           locate
the tests that were done and figure out what the tester was thinking if it wasn’t
you, and             then try and decide whether or not it even applies to the new code. By
the time you figure that             stuff out I would imagine you could have written
several test cases according to the latest                     iteration.

  • The test environment might be different.

          This is true as well, things seemingly change
frequently so you may have changed the                         environment and once again wasting time
seeing what you or someone else did.

The bottom line here is that while in some cases the old
data may help, but more than likely it will, in my opinion slow you down. One
more thing I think can happen is can stagnate your thought process as you are
looking at old ideas instead of coming up with new ideas.
http://www.testthisblog.com/2016/03/start-from-scratch-vs-old-test.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.testthisblog.com/2016/03/couple-automated-checks-with-product.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.testthisblog.com/2016/02/automated-checking-is-very-human.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.softwaretestingmagazine.com/knowledge/how-to-give-better-code-reviews/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+SoftwareTestingMagazine+%28Software+Testing+Magazine%29
http://www.developsense.com/blog/2016/05/testers-dont-prevent-problems/

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Whether or not to use old test data

This week I read a great blog on starting from scratch or
using old test documentation. The writer formed the blog based on a question
asked by one of his fellow testers, “How can I find old test documentation for
a completed feature so I can re-use those test on a similar new feature?”.
My initial thought was that’s actually not a bad idea, but
the more I read the more I was swayed and started thinking about times when I
was either asked about a similar situation or posed the same question. Though I
wasn’t software testing at the time nor even in the industry this can be
applied to other scenarios as well.
While I do think that it is a good idea to track and refer
to past tests to see what has been done, I agree with the writer that “a
skilled tester can usually come up with better tests…today, from scratch.” He
makes many valid points and I will go over a couple that I thought to me stood
out, you can read the blog to get the rest if you’d like.
  • ·        
    A skilled tester knows more about testing today
    than they did last month.

         How true. The more you do something the
more you learn about it and the better you become at          it.
  • The product-under-test is different today than
    it was last month.  It might have new code, refactored code, more users,
    more data, a different reputation, a different platform, a different time of
    the year, etc.

          As the development process moves through
the different iterations, things change. Looking at             past tests may help, but
more probably than not it will probably slow you down. You have first           locate
the tests that were done and figure out what the tester was thinking if it wasn’t
you, and             then try and decide whether or not it even applies to the new code. By
the time you figure that             stuff out I would imagine you could have written
several test cases according to the latest                     iteration.

  • The test environment might be different.

          This is true as well, things seemingly change
frequently so you may have changed the                         environment and once again wasting time
seeing what you or someone else did.

The bottom line here is that while in some cases the old
data may help, but more than likely it will, in my opinion slow you down. One
more thing I think can happen is can stagnate your thought process as you are
looking at old ideas instead of coming up with new ideas.
http://www.testthisblog.com/2016/03/start-from-scratch-vs-old-test.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.testthisblog.com/2016/03/couple-automated-checks-with-product.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.testthisblog.com/2016/02/automated-checking-is-very-human.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.softwaretestingmagazine.com/knowledge/how-to-give-better-code-reviews/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+SoftwareTestingMagazine+%28Software+Testing+Magazine%29
http://www.developsense.com/blog/2016/05/testers-dont-prevent-problems/

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Whether or not to use old test data

This week I read a great blog on starting from scratch or
using old test documentation. The writer formed the blog based on a question
asked by one of his fellow testers, “How can I find old test documentation for
a completed feature so I can re-use those test on a similar new feature?”.
My initial thought was that’s actually not a bad idea, but
the more I read the more I was swayed and started thinking about times when I
was either asked about a similar situation or posed the same question. Though I
wasn’t software testing at the time nor even in the industry this can be
applied to other scenarios as well.
While I do think that it is a good idea to track and refer
to past tests to see what has been done, I agree with the writer that “a
skilled tester can usually come up with better tests…today, from scratch.” He
makes many valid points and I will go over a couple that I thought to me stood
out, you can read the blog to get the rest if you’d like.
  • ·        
    A skilled tester knows more about testing today
    than they did last month.

         How true. The more you do something the
more you learn about it and the better you become at          it.
  • The product-under-test is different today than
    it was last month.  It might have new code, refactored code, more users,
    more data, a different reputation, a different platform, a different time of
    the year, etc.

          As the development process moves through
the different iterations, things change. Looking at             past tests may help, but
more probably than not it will probably slow you down. You have first           locate
the tests that were done and figure out what the tester was thinking if it wasn’t
you, and             then try and decide whether or not it even applies to the new code. By
the time you figure that             stuff out I would imagine you could have written
several test cases according to the latest                     iteration.

  • The test environment might be different.

          This is true as well, things seemingly change
frequently so you may have changed the                         environment and once again wasting time
seeing what you or someone else did.

The bottom line here is that while in some cases the old
data may help, but more than likely it will, in my opinion slow you down. One
more thing I think can happen is can stagnate your thought process as you are
looking at old ideas instead of coming up with new ideas.
http://www.testthisblog.com/2016/03/start-from-scratch-vs-old-test.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.testthisblog.com/2016/03/couple-automated-checks-with-product.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.testthisblog.com/2016/02/automated-checking-is-very-human.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.softwaretestingmagazine.com/knowledge/how-to-give-better-code-reviews/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+SoftwareTestingMagazine+%28Software+Testing+Magazine%29
http://www.developsense.com/blog/2016/05/testers-dont-prevent-problems/

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Whether or not to use old test data

This week I read a great blog on starting from scratch or
using old test documentation. The writer formed the blog based on a question
asked by one of his fellow testers, “How can I find old test documentation for
a completed feature so I can re-use those test on a similar new feature?”.
My initial thought was that’s actually not a bad idea, but
the more I read the more I was swayed and started thinking about times when I
was either asked about a similar situation or posed the same question. Though I
wasn’t software testing at the time nor even in the industry this can be
applied to other scenarios as well.
While I do think that it is a good idea to track and refer
to past tests to see what has been done, I agree with the writer that “a
skilled tester can usually come up with better tests…today, from scratch.” He
makes many valid points and I will go over a couple that I thought to me stood
out, you can read the blog to get the rest if you’d like.
  • ·        
    A skilled tester knows more about testing today
    than they did last month.

         How true. The more you do something the
more you learn about it and the better you become at          it.
  • The product-under-test is different today than
    it was last month.  It might have new code, refactored code, more users,
    more data, a different reputation, a different platform, a different time of
    the year, etc.

          As the development process moves through
the different iterations, things change. Looking at             past tests may help, but
more probably than not it will probably slow you down. You have first           locate
the tests that were done and figure out what the tester was thinking if it wasn’t
you, and             then try and decide whether or not it even applies to the new code. By
the time you figure that             stuff out I would imagine you could have written
several test cases according to the latest                     iteration.

  • The test environment might be different.

          This is true as well, things seemingly change
frequently so you may have changed the                         environment and once again wasting time
seeing what you or someone else did.

The bottom line here is that while in some cases the old
data may help, but more than likely it will, in my opinion slow you down. One
more thing I think can happen is can stagnate your thought process as you are
looking at old ideas instead of coming up with new ideas.
http://www.testthisblog.com/2016/03/start-from-scratch-vs-old-test.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.testthisblog.com/2016/03/couple-automated-checks-with-product.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.testthisblog.com/2016/02/automated-checking-is-very-human.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+EricJacobsonSoftwareTestingBlog+%28Test+This+Blog+-+Eric+Jacobson%27s+Software+Testing+Blog%29
http://www.softwaretestingmagazine.com/knowledge/how-to-give-better-code-reviews/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+SoftwareTestingMagazine+%28Software+Testing+Magazine%29
http://www.developsense.com/blog/2016/05/testers-dont-prevent-problems/

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Wireframe Testing

A lot of software testing focuses on testing the code, which is very important, but there is another area of testing to consider, the user experience. When it comes to designing a product it is important to keep in mind who will be using it and what they are expecting. This area of testing ranges depending on the nature of the software. If, for example, you are developing software that is to be server based and will be run from command line it will require less time than a program that is to be used by the average employee.

It is a good idea to start this testing before you have invested too much time in developing the final user interface. A quote by Frank Lloyd Wright that summarizes this is “You can use an eraser on the drafting table or a sledge hammer on the job site.”

One way to accomplish this is to make use of wireframe testing. Wireframe testing is a method of testing that involves generating a mock up so that the end user can get a feel for what the final program will look like and how it will behave. There is also a variation where an expert analyzes the software instead of the end user.

Wireframes can vary in details. The simplest form may be a simple sketch the allows the user to see how items are laid out. More detailed wireframes fall into to categories high fidelity and low fidelity. Low fidelity wireframes are mock ups that provide a fairly similar look to the final product and some functionality where as high fidelity wireframes are very similar to the final product in look and feel.

Original Articles:
http://curioustester.blogspot.com/2015/08/wireframes-testing-part-i.html
http://curioustester.blogspot.com/2015/09/wireframes-testing-part-ii-how-did-i-do.html

From the blog CS@WSU – :(){ :|: & };: by rmurphy12blog and used with permission of the author. All other rights reserved by the author.

Test Driven Development

This week I was reading a book called Test Driven Development by Viktor Farcic. The first chapter is about why we need TDD.

The book list a few problems that all software developers face. I have listed a few from the book:

  • Most, if not all, of your tests are manual, or you don’t have tests at all.
  • Automated tests are written and executed when it’s too late for them to provide any real value for the project.
  • The maintenance cost is too high.
  • Documentation is never up to date.
  • Team is spending too much time trying to figure out what some method or class does.

TDD does not magically solve any of these problems, but it sets us in the path toward the solution. TDD speeds up the time-to-market, enables easier refactoring, helps to create better design, and fosters looser-coupling.

The book goes on to explain something called the Red-Green-Refactor process. The procedure is simple:

  1. Write a test
  2. Run all tests
  3. Write the implementation code
  4. Run all tests
  5. Refactor
  6. Run all tests

Speed in key in this process; never spend more than a minute on writing tests or implementation. It’s like a game of ping pong, the game is very fast. Write a short test and run all tests (ping), write the implementation and run all tests (pong). Repeat until it’s time to refactor and confirm all tests are passing (score). It is important to understand that TDD is not about testing, it is a process to develop high quality software fast.

The two really interesting side effects of TDD are Executable documentation and No debugging. In TDD the tests serve as the documentation. If wan’t to find out what a particular method does, read the tests associated with it. This solves the problem of out of date documentation.

The second side effect is that we almost never need to debug applications we’re working on. We almost never debug because there is rarely a reason to debug. When the tests are written before the code we can have high confidence that the code is working as expected. And since we build the software in very small steps, any errors that might occur is very easily resolved.

I went on to read and follow chapter 3 and it really helped me improve my understanding of TDD.

 

From the blog Software Testing – The blog about software by Sudarshan and used with permission of the author. All other rights reserved by the author.

Exploratory Testing(Week 6)

What is exploratory testing? Exploratory testing is a type of black box testing where you do not need to worry about the internal coding of the software. It is all about simultaneously learning. This kind of testing means the tester has the freedom to do whatever they want. It all depends on the tester’s creativity. In exploratory testing you do not write test cases in advance, first you learn about the software then you write test cases for it. 

So let’s go through some of the advantages and disadvantages of exploratory testing. Some of the good things about it is that it takes less preparation, it helps to find major bugs early because testers main focus is on error causing functionality. Can be done quickly and time efficiently. A bad thing about using this kind of testing is sometimes learning the application or software can be difficult. Also you do not really know when to stop the testing because this kind of testing has definite test cases to execute. Lastly, this kind of testing is only possible when you have skilled and domain specified testing teams. 

Exploratory Testing: http://www.software-testing-tutorials-automation.com/2016/10/exploratory-testing.html#more

 

Other articles i looked at:

http://www.software-testing-tutorials-automation.com/2016/10/adhoc-testing.html

http://www.software-testing-tutorials-automation.com/2016/10/globalization-testing-and-localization.html

http://www.software-testing-tutorials-automation.com/2016/10/state-transition-testing.html

http://www.software-testing-tutorials-automation.com/2016/09/what-is-decision-table.html

From the blog CS@Worcester – Site Title by jonathanpaizblog and used with permission of the author. All other rights reserved by the author.