So a big debate that is heard a lot is whether to use Exploratory testing or Scripted. Exploratory testing is where you go in and you search the app specifically looking for bugs. You are going to search anywhere and everywhere based on the design. You will also try things out side the design. Basically think of it as you are on a safari hunting for bugs. You are exploring new territory looking for things that are out of the ordinary. This is a very widely used way of testing and also very popular.
What is Scripted testing? Well script testing you have a set script based on the design and how QA will be testing the software. With this you can get through and make sure certain points are hit. If something needs to be tested then you add it to the script. This is what you use a test plan for and you can read more about that in my first couple blogs. Think of it as a play and if it does not go a written put in a bug.
What are the benefits of using both? There is more benefits to using both then there are to not using one or the other. Scripted is really good and getting a through test but may miss something. Exploratory will help you find what you are missing but is no where near as through. This in hopes makes our below pie chart have less not found.
Conclusion: Use both in everyday testing.
A while ago I read an article on the future of agile testing. When reading through I saw this thing called Pair Testing so I looked it up and found a good article at this link. This is when the Developer and QA work together testing. This way they will hit things normally they would not hit separately plus things can be fixed right there on the spot or you can at least you can get the information the developer needs to fix the issue. This will also help with QA, Dev relationship as they will work closely and see how each other operates. This we be a good idea for doing 60-90 minutes a week.
Not only is this a good idea with a dev and a QA working together we have found within our own QA that 2 QA testing together you will hit issues neither of you have hit together. This is because you are both different testers and will test differently and so together you will try things neither have thought of. Also you will be able to track down more detail since you both have different ways to figure out the issue. You can also write a very thorough Test Plan if 2 of you work together to hit all the test cases. So do I feel Paired Testing is the wave of the future? I believe I think it is.
To know more I suggest you go to Http://softwaredevelopmentisfun.blogspot.com/2008/07/pair-testing.html
When working in QA you will receive tickets submitted by clients, support, or various other people. It is your job to go through them using these 5 steps.
Receive (the ticket)
Verify (that it is a problem)
Justify the Problem (is it user error over defect)
Report Problem (to engineering)
QA Hipster is a Quality Assurance Technical Lead for an software company, mostly working with Macs. I have been in the field since September 2013, and have a bachelor's degree in Management Information Services. I started my studies at Iowa State in Software Engineering. I have been working on moving my company forward with the latest QA techniques.