So I have reached my limit for uploaded Gifs, awesome I know. So here are links to the Gifs.
When a new build comes out with fresh features to check
What your family hears when you explain your day
When you hit and unexpected bug when testing
When you reproduce a complicated bug
When you get a new build and everything is broken
Finding the requirements for the software can be hard but a tester has to know when the software breaks and what it takes to run the software. If the tester runs at minimum requirements and it breaks then the requirements are wrong. Some times it is up to the developers what it runs on, some times upper management, and sometimes a tester runs several test. This will also have to be well analyzed and documented. You will also have to take into consideration your market and what kind of computer they have. If it takes to expensive of a computer you loose your market.
Remember to take all this into consideration and many more when setting your software requirements.
This is the first of many blogs that I will be writing on the Software Development Process. There is a lot to it and several options. Each company will apply a different mythology for there process. It could be agile, spiral, prototyping, or the dreaded waterfall. Over the years though each company starts with one and may switch to another but they are searching for the best one for them.
The Methologies did not appear until the 1960's starting with the life cycle and progressing through out the years with Agile being the latest and from what I hear greatest. Since I will be going through each methodology and aspect I will end here and come back next week to blog about one of the Core Activities which is Requirements.
So what is end to end testing? Just like in the maze you are to get from point A of the program to point be. So in the example in the link I am using this week it is from login to logout. The example from Software Testing Help is below:
End to End testing of a Gmail account will include following steps:
These test are done from the view point of the end user. What is their workflow and how will they move from point A to B using your software. These are ran to make sure that the user can run through their workflow with no issue. As seen in the maze picture there are times where you might off road or 'Exploratory Test but the end result and the beginning result are the main points. In the example you run through logging in then through basic steps that any user would experiance. but follow a vertical work flow of the side bar. Then you logout.
So now that you know go and find something you are use to and create your own maze of test.
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.