Category: Archived

            <div><div class="wsite-image wsite-image-border-none " style="padding-top:10px;padding-bottom:10px;margin-left:0;margin-right:0;text-align:center"> <a> <img src="http://qahipster.weebly.com//uploads/8/1/4/4/8144013/common-sense_orig.png" alt="Picture" style="width:auto;max-width:100%"> </a> <div style="display:block;font-size:90%"></div> </div></div>  <div class="paragraph">​This week the Ministry of Testing Bloggers club has decided on "What’s the non-technical skill that every tester should have, but most don’t seem to?"<br><br>Being a tester move have a very technical mind. A lot of time with intelligent technical people they lack basic common sense. I have seen mountains made out of mole hills, useless tickets, and tickets that no one will ever fix. The button is 2 pixels off... ain't nobody got time for that. A new feature has some bugs do to a weird workflow. Ok we can fix it but we don't need to hold shipping to beta when there is a work around and most people will not use that workflow. Plus a new feature is not breaking current functionality. Take some time to think before standing up for that bug. Yes there are bugs that need standing up for and by golly you do it but make sure it is worth it and not a waste of everyones time. Use Common sense when judging the bug. </div>

            <div><div class="wsite-image wsite-image-border-none " style="padding-top:10px;padding-bottom:10px;margin-left:0px;margin-right:0px;text-align:center"> <a href="https://www.amazon.com/Head-First-Java-Kathy-Sierra/dp/0596009208" target="_blank" rel="noopener"> <img src="http://qahipster.weebly.com//uploads/8/1/4/4/8144013/51gsycdh-tl-sx430-bo1-204-203-200_orig.jpg" alt="Picture" style="width:auto;max-width:100%"> </a> <div style="display:block;font-size:90%"></div> </div></div>  <div class="paragraph">This week the Ministry of Testing Bloggers Club is tackling "What non-testing focussed book do you wish you’d been given on your first day testing."<br><br>I have been working in the realm of manual testing for years. Over that time I have been given a lot of lead way and have been able to do more then our average tester. This is because I took a lot of programing courses in University.  Being able to look at the code and understand what is going on and understanding why something breaks has helped me loads in testing.<br><br>It allows me to find new tools, learn coding for fixing minor bugs or just figuring out a little more then the manual tester. I think all QA should have some basic understanding of Object oriented programing. Not only does it help you become a better tester your developers listen to you more. <br><br>So when you have time learn some coding. This Head First book about Java is great but you can also try <a href="https://www.codecademy.com/learn" target="_blank" rel="noopener">Codecademy</a>.</div>

            <div><div class="wsite-image wsite-image-border-none " style="padding-top:10px;padding-bottom:10px;margin-left:0;margin-right:0;text-align:center"> <a> <img src="http://qahipster.weebly.com//uploads/8/1/4/4/8144013/to-be-not-to-be_orig.jpg" alt="Picture" style="width:auto;max-width:100%"> </a> <div style="display:block;font-size:90%"></div> </div></div>  <div class="paragraph">This sprint for the Ministry of Testing Bloggers Club the topic was "Critic some widely known/accepted concept in the testing community" Being that I have never really been a full fledged member of a testing community I don't know what they widely accept.<br><br>The one thing for years it was thought that testers were not needed, the clients could test the software and give feedback as soon as it was released. That caused a lot of issues with calling clients to tell them things have gone horribly wrong. Then the age of manual testers came and all was well, but as software evolves so does Testing. The age of automated testing has been happening everywhere. <br><br>A belief that has also been spreading in bigger companies is that they can just patch it so feel free to release it to the customer. We can fix it when they complain as patches are so readily available. This is very prevalent in the gaming community to the point where sometimes you have to pay to fix a bug. <br><br>With automated testing growing some think that the manual tester is a dinosaur no longer needed and all they need it automation. Robots then rule the world and order is obtained. Automation can not test everything, the human brain is more complex and is needed for full testing. Automation is a great tool for repetitive and simple test.<br><br>What is really needed is a good balance of automation and manual testing. Automation does basic test leaving manual testing to be more in dept.</div>

            <span class="imgPusher" style="float:left;height:0px"></span><span style="display: table;width:auto;position:relative;float:left;max-width:100%;;clear:left;margin-top:0px;*margin-top:0px"><a><img src="http://qahipster.weebly.com//uploads/8/1/4/4/8144013/tenor_1_orig.gif" style="margin-top: 5px; margin-bottom: 10px; margin-left: 0px; margin-right: 10px; border-width:1px;padding:3px; max-width:100%" alt="Picture" class="galleryImageBorder wsite-image"></a><span style="display: table-caption; caption-side: bottom; font-size: 90%; margin-top: -10px; margin-bottom: 10px; text-align: center;" class="wsite-caption"></span></span> <div class="paragraph" style="display:block;">Well, I am back after 2 years off, and I have a lot of new stuff to blog about. I have recently joined the <a href="https://club.ministryoftesting.com/c/bloggers-club" target="_blank" rel="noopener">Ministry of Testing’s Blogger’s Club</a>, a group dedicated to blogging about testing by providing topics, blogging together on general topics, and being the motivation we all need. I hope with their support and adding 2 more years of testing under my belt, I can create a better blog for everyone.<br><br>​​​​The first topic is "a technical tip every tester should know" so I went with give yourself time to learn and grow as a tester. Something this blog supported in the past and will continue to support in the future.<br><br>I have worked for a company manual testing for 5 years now. In this time there has been little to no growth in our QA department. Just retesting the same parts of the software over and over. Waiting for when a new feature can be tested to pull you away from the monotonous test you run through on a daily basis. If our QA begins looking for other jobs, they realize that our company is behind the times, as manual testers, are coming to an end. Manual tests are now only a part of what most QA do in this modern world. A lot of our employees hunger to grow, have something they can achieve, and while others like where they are and don't want change. <br><br>However, I have been fortunate my company has allowed me to learn and try other things, becoming a better tester. They allowed me to do this because I have a coding background and the tenacity to ask. So they trusted me run new tools, fix minor bugs, and become the one everyone goes to when they need help. Still most of what I did was manual testing with a sprinkling of extra fun tools. I was still stagnating at as tester in my community when all other companies in my location are moving to include automated testing. <br><br>Something then happened that changed everything. Our company got some new management which listened to our employees. They allowed our developers to launch a new plan for our software taking us into the future. With these changes they asked if QA could begin automated testing with the new project. So all those years building the trust they put me to learning and researching Serenity, Cucumber, Selenium and Postman. I then get to teach the others in my department. The company is finally moving forward with a plan one Developer had for years for our software, and what I been proposing for years is finally coming to the our company.<br><br>The drawback with learning and growing in such a short time is growing pains as my head explodes with knowledge and headaches. It would be nice for every company to allow a day of learning similar to what Google has done in the past and has become a growing part of Agile culture. Don't stagnate you're learning or try to do it all at once because it all of a sudden becomes relevant.<br><br>Learning new things in your industry helps you become better at your job. It gives you more responsibilities, makes you feel valued as a team member. When you learn and grow, the company learns and grows with you. <br><br>It was Gandhi who said, "Be the change you want to see in the world." <br><br>Be the change you want to see in your company. Sometimes it takes patience to move forward. Sometimes it takes only one person to believe in your idea. When you learn and grow as a tester, you learn and grow as a person. <br><br>Google is your best friend when it comes to learning and researching. Bookmark links and document everything you learn so you can return to it later. Documenting helps you to not forget what you learned and allows you to share your newfound knowledge with others. When you document and share you become an expert because it helps your brain retain the knowledge you have learned better. </div> <hr style="width:100%;clear:both;visibility:hidden;">

            <div><div class="wsite-image wsite-image-border-none " style="padding-top:10px;padding-bottom:10px;margin-left:0;margin-right:0;text-align:center"> <a> <img src="http://qahipster.weebly.com//uploads/8/1/4/4/8144013/9708296_orig.jpg" alt="Picture" style="width:auto;max-width:100%"> </a> <div style="display:block;font-size:90%"></div> </div></div>  <div class="paragraph" style="text-align:left;">I worked on this site and blogging about testing for 10 months and it was great to see it grow and to see everyone reading and responding to what I had to offer. This was a great learning experience and I would not give it away for anything in the whole world. The reason I took a break was in September my Best friend of 26 years died in a tragic motor cycle accident and it rocked me. I was unable to continue with some of my projects and they suffered for it. I am now looking at this new year with fresh eyes.<br><br>This site will continue to be up for another 325 days before it will cease to exist. Please fill free to go over all the knowledge I put into this site and feel free to contact me on Twitter or through the site. <br><br>Thanks so much for reading my blog.<br></div>

            <div><div class="wsite-image wsite-image-border-none " style="padding-top:10px;padding-bottom:10px;margin-left:0;margin-right:0;text-align:center"> <a> <img src="http://qahipster.weebly.com//uploads/8/1/4/4/8144013/840347804.jpg" alt="Picture" style="width:100%;max-width:590px"> </a> <div style="display:block;font-size:90%"></div> </div></div>  <div class="paragraph" style="text-align:left;">Lately I have had some things happen in my personal life that I have not been able to keep up with all my side projects. I will be back up running as soon as I can and may even be next week. But this week I am taking a break to let my personal issues cool down.<br><br>Remember everything is a test and your job is pass it or find a workaround.<br><br>Thanks<br></div>

            <div class="paragraph" style="text-align:left;">So I have reached my limit for uploaded Gifs, awesome I know. So here are links to the Gifs.<br><br><a target="_blank" href="http://giphy.com/gifs/DuWay0MoeQxWM" rel="noopener">When a new build comes out with fresh features to check</a><br><br><a target="_blank" href="http://giphy.com/gifs/fetty-wap-my-way-KbQ1z8GAxXVN6" rel="noopener">What your family hears when you explain your day</a><br><br><a target="_blank" href="http://giphy.com/gifs/cheezburger-hello-animation-6Xbr4pVmJW4wM" rel="noopener">When you hit and unexpected bug when testing</a><br><br><a target="_blank" href="http://giphy.com/gifs/brain-sheldon-big-bang-theory-u4KibgMsDLWM0" rel="noopener">When you reproduce a complicated bug</a><br><br><a target="_blank" href="http://giphy.com/gifs/HteV6g0QTNxp6" rel="noopener">When you get a new build and everything is broken</a><br></div>

            <div><div class="wsite-image wsite-image-border-none " style="padding-top:10px;padding-bottom:10px;margin-left:0;margin-right:0;text-align:center"> <a> <img src="http://qahipster.weebly.com//uploads/8/1/4/4/8144013/282741024.jpg" alt="Picture" style="width:100%;max-width:800px"> </a> <div style="display:block;font-size:90%"></div> </div></div>  <div class="paragraph" style="text-align:left;">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.<br><br><a target="_blank" href="https://en.wikipedia.org/wiki/Requirements_analysis" rel="noopener">Requirements Analysis</a><br><ul style=""><li style=""><a style="" href="https://en.wikipedia.org/wiki/Requirements_elicitation" title="Requirements elicitation">Eliciting requirements</a>:(e.g.  the project charter or definition), business process documentation, and  stakeholder interviews. This is sometimes also called requirements  gathering.</li><li style="">Analyzing requirements: determining whether the stated requirements  are clear, complete, consistent and unambiguous, and resolving any  apparent conflicts.</li><li style="">Recording requirements: Requirements may be documented in various  forms, usually including a summary list and may include natural-language  documents, <a style="" href="https://en.wikipedia.org/wiki/Use_case" title="Use case">use cases</a>, <a style="" href="https://en.wikipedia.org/wiki/User_story" title="User story">user stories</a>, or process specifications.</li></ul>Remember there is several things besides the software and the customers who effect requirements. Such as Architecture what other programs are you using Java, squeal? Is the structure meeting the requirements? the design? the behavior? Allocated? <br><br>Remember to take all this into consideration and many more when setting your software requirements. <br><br><span></span><br><span></span></div>

            <div><div class="wsite-image wsite-image-border-none " style="padding-top:10px;padding-bottom:10px;margin-left:0;margin-right:0;text-align:center"> <a> <img src="http://qahipster.weebly.com//uploads/8/1/4/4/8144013/200832500.gif" alt="Picture" style="width:100%;max-width:691px"> </a> <div style="display:block;font-size:90%"></div> </div></div>  <div class="paragraph" style="text-align:left;">This is the first of many blogs that I will be writing on the <a title="" target="_blank" href="https://en.wikipedia.org/wiki/Software_development_process" rel="noopener">Software Development Process</a>. 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. <br><br>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. <br></div>

            <div><div class="wsite-image wsite-image-border-none " style="padding-top:10px;padding-bottom:10px;margin-left:0;margin-right:0;text-align:center"> <a> <img src="http://qahipster.weebly.com//uploads/8/1/4/4/8144013/217470349.png" alt="Picture" style="width:auto;max-width:100%"> </a> <div style="display:block;font-size:90%"></div> </div></div>  <div class="paragraph" style="text-align:left;">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 <a target="_blank" href="http://www.softwaretestinghelp.com/what-is-end-to-end-testing/" rel="noopener">Software Testing Help</a> is below:<br></div>  <blockquote style="text-align:left;">End to End testing of a Gmail account will include following steps:<br><span style=""></span><br><span style=""></span> <ol style=""><li style="">1. Launching Gmail login page through URL.</li><li style="">2. Logging into Gmail account by using valid credentials.</li><li style="">3. Accessing Inbox. Opening Read and Unread emails.</li><li style="">4. Composing new email, reply or forward any email.</li><li style="">5. Opening Sent items and checking emails.</li><li style="">6. Checking mails in Spam folder</li><li style="">7. Logging out of Gmail application by clicking ‘logout’</li></ol></blockquote>  <div class="paragraph" style="text-align:left;">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. <br><br>So now that you know go and find something you are use to and create your own maze of test.<br></div>