<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-6272649600366232306</atom:id><lastBuildDate>Tue, 23 Dec 2014 14:46:44 +0000</lastBuildDate><title>Get Testy</title><description>A Test Analysts Point of View</description><link>http://gettesty.blogspot.com/</link><managingEditor>noreply@blogger.com (Yehuda Miller)</managingEditor><generator>Blogger</generator><openSearch:totalResults>7</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6272649600366232306.post-1914016855549361043</guid><pubDate>Thu, 18 Sep 2014 12:59:00 +0000</pubDate><atom:updated>2014-09-18T15:59:39.611+03:00</atom:updated><title>Priority vs. Severity</title><description>Ok, ok, I admit that this issue has been covered before but I want to bring it up here anyway. I just started a new job and, although I am the &quot;new guy&quot;, there are two people here who are within the first two months of their testing career. New out of college, these guys haven&#39;t yet been indoctrinated by the formalities of organizations such as ISO or ISTQB. I feel I have a duty to help them see the beauty of testing.&lt;br /&gt;&lt;br /&gt;Earlier today, one of these guys asked me what they thought was a simple, innocuous question: How do I determine the priority of a bug in Jira?&lt;br /&gt;&lt;br /&gt;The following is what I told him. It was most likely way more than he was asking for but I felt it was important to convey the point. &lt;br /&gt;&lt;br /&gt;&lt;blockquote class=&quot;tr_bq&quot;&gt;Yehuda Miller: what do you mean determine? Assign priority or see what a bugs priority is?&lt;br /&gt;New Guy: assign&lt;br /&gt;Yehuda Miller: The answer is not so simple. Priority is usually used to mean two different things: priority AND severity. Priority really means: how important is it to fix this issue right now? Severity means: how &quot;bad&quot; is this bug? A really really tiny bug could be majorly important (ex: a misspelled word on the homepage that results in a vulgarity). This is a really simple issue to fix, however it needs to be made priority number one. On the other hand, there could be a report in the site utils that just flat out won&#39;t work. Server Error 500 or something like that. But it&#39;s a report that needs to be run once a year and the next time is in 11 months. Therefore, high severity but low priority.&lt;/blockquote&gt;&lt;br /&gt;I think we as testers should push our organizations (if they are not doing it already) to have priority and severity as two different categories to define our bugs. Without it, the picture is incomplete.</description><link>http://gettesty.blogspot.com/2014/09/priority-vs-severity.html</link><author>noreply@blogger.com (Yehuda Miller)</author><thr:total>2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6272649600366232306.post-619907034183002861</guid><pubDate>Tue, 14 May 2013 20:19:00 +0000</pubDate><atom:updated>2013-05-14T23:19:13.013+03:00</atom:updated><title>Concurrent Testing</title><description>One of the sessions I attended up at Star Canada was a really fun session called Concurrent Testing Games. It was presented by Nate Oster from Code Squads.&lt;br /&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;The talk actually revolved around an interactive game he designed to help show the pitfalls of &quot;throwing code over the wall&quot; from development to QA. It really showed off the benefits of agile teams and how integral it is to include testers in those teams.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;He started by talking about how when a software development team wants to &quot;go agile&quot; it often just compresses timelines and makes projects smaller but becomes a mini-waterfall environment. This just causes frustration and makes people scream &quot;I hate this agile stuff!&quot;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Instead, he said, with agile teams the testing should begin from the beginning of the process. The team as a whole should identify the happy path tests and then build up around those tests. Add in complexity only after the code has been completed and tested. This way new development is only done on clean code. If you&#39;ve verified that a piece of code is (relatively) bug free, you are more confident coding on top of it. This will increase the velocity of the team and, with proper implementation of automation, free the tester up to use his or her best skills, exploration of new features, more often.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;He left us with a challenge. Next time you are working on a new project, do this for one of your stories. Pick a story, explain to the developer what you want to do (and obviously get his buy in to help you) and go.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Let the games begin!&lt;/div&gt;</description><link>http://gettesty.blogspot.com/2013/05/concurrent-testing.html</link><author>noreply@blogger.com (Yehuda Miller)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6272649600366232306.post-2739951574014582349</guid><pubDate>Thu, 02 May 2013 15:26:00 +0000</pubDate><atom:updated>2013-05-02T21:11:39.184+03:00</atom:updated><title>Is QA Really The Roadblock?</title><description>Anyone who works in quality assurance knows that in most organizations we are looked at as roadblocks or bottlenecks. &quot;Why was the release late?&quot; Is often answered by &quot;QA took more time than expected to test it.&quot; Taken at face value, this exchange sure does seem to incriminate QA. I&#39;d like to turn this idea on its head. &lt;br /&gt;&lt;br /&gt;There are software products out on the open market right now that have never gone through testing by an official QA team. Many open source tools, especially small ones, are written by a single developer out of his mothers basement. Many of them work really well too. &lt;br /&gt;&lt;br /&gt;As a software product grows in scope the dependencies and complexity grow as well. Maybe there are now 2 or 3 developers involved in the programming process. Even if they each test their own code and do code reviews, they can&#39;t be sure they fully understand other aspects of the system. This group grows and grows until maybe you have quite a large development team.&lt;br /&gt;&lt;br /&gt;This is often when an independent testing team is brought in. It&#39;s the task of this team of testers to know the system inside out, backwards and forwards and upside down. Maybe not the inner workings of the code (although that doesn&#39;t hurt) but of how the system works, what the intended functionality is etc. This team could be assembled for one of two reasons. 1. &quot;My competitor has a QA team so I want one too.&quot; or 2. &quot;I want to offer my stakeholders the best product possible. As it would be impossible and impractical to have my developers take the time to review and test every new feature coded by every developer, let me assemble an independent team dedicated to the testing.&quot; Usually, the latter option is the true reason. &lt;br /&gt;&lt;br /&gt;It is the primary job of QA to provide information. As Lloyd Roden said in his keynote speech &quot;Surviving or Thriving: Top Ten Lessons for the Professional Tester&quot; at Star East conference 2013, it&#39;s not the job of QA to decide when to release. When asked if something can be released, QA&#39;s response should always be &quot;Yes! However...&quot; and provide current statistics on the status of the project. &lt;br /&gt;&lt;br /&gt;It&#39;s all a matter of asking the right questions. Instead of asking &quot;why is the release stuck in QA?&quot; try asking &quot;what are acceptable issues to release to production?&quot; If QA is always answering &quot;Yes! However...&quot; then the real roadblock or bottleneck is the person who values the quality of the software and the advice of the QA department. And chances are its not even a roadblock, as the extra time often leads to the prevention of issues which would negatively affect stakeholders. It just depends on how you look at it. </description><link>http://gettesty.blogspot.com/2013/05/is-qa-really-roadblock.html</link><author>noreply@blogger.com (Yehuda Miller)</author><thr:total>3</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6272649600366232306.post-942464653494265584</guid><pubDate>Mon, 29 Apr 2013 20:54:00 +0000</pubDate><atom:updated>2013-05-02T23:43:15.710+03:00</atom:updated><title>Not Testing</title><description>One of the best lectures I heard in Toronto at STAR Canada was by a guy named Eric Jacobson about when not to test. It was a very interesting concept. We all came from near and far to learn about testing techniques and here&#39;s a guy telling us when we should not even bother. Very strange and I was intrigued.&lt;br /&gt;&lt;br /&gt;Each company and testing team will have to interpret the message slightly differently but the main point was this: just because it exists doesn&#39;t mean it&#39;s the highest priority to test. The crux of the talk was that before we blindly test anything and everything that is coded, take some time to analyze the value of testing certain things before spending the time.&lt;br /&gt;&lt;br /&gt;Something to think about is the potential risk it could pose in production. If the code were released, what possible impact could it have on the production environment and customers? Not much? Maybe skip testing it and focus on a high risk issue. If it&#39;s the difference between testing a typo and a shopping cart issue, the shopping cart issue should probably take preference.&lt;br /&gt;&lt;br /&gt;Another thing to consider is if someone else can help you test it. Maybe a BA entered a ticket for a bug in the QA environment that they discovered. You can certainly test it when the fix comes through but you could also ask that BA to retest it and make sure to have him or her send you some proof of testing. This way, he or she will be able to run through the exact scenario they were doing when they originally encountered the issue.&lt;br /&gt;&lt;br /&gt;Have you ever had situations where you had to prioritize your testing? What did you do in such an event? How did you prioritize? Comments below.&lt;br /&gt;&lt;br /&gt;Credit for this topic goes to Eric Jacobson. See his blog at &lt;a href=&quot;http://www.testthisblog.com/&quot;&gt;www.TestThisBlog.com&lt;/a&gt;.</description><link>http://gettesty.blogspot.com/2013/04/not-testing.html</link><author>noreply@blogger.com (Yehuda Miller)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6272649600366232306.post-6377713317233635641</guid><pubDate>Fri, 19 Apr 2013 13:24:00 +0000</pubDate><atom:updated>2013-04-19T16:24:54.553+03:00</atom:updated><title>Well, It Works in Dev</title><description>It&#39;s broken in QA but works in dev...&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;We&#39;ve all been here before. It&#39;s so annoying because it has to get fixed before production but you just can&#39;t get the developers system to produce the failure. Also, you can&#39;t just chock it up to the environment because it&#39;s blocking your testing of other new and existing features. Ugh...&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;While I cannot control how the environments act, I definitely can control my actions. One thing I&#39;ve learned is it&#39;s not the developers fault that the issue isn&#39;t occurring on his or her system. Getting angry and frustrated at him or her is for sure not the answer here. In most cases they are more frustrated than you are because they are the ones that have to fix it.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;What are some things you do when this occurs in your work environment?&lt;/div&gt;</description><link>http://gettesty.blogspot.com/2013/04/well-it-works-in-dev.html</link><author>noreply@blogger.com (Yehuda Miller)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6272649600366232306.post-6676164340052800259</guid><pubDate>Mon, 15 Apr 2013 21:30:00 +0000</pubDate><atom:updated>2013-04-16T00:30:00.400+03:00</atom:updated><title>Test Case Management</title><description>So, somehow, I&#39;ve never worked in a company that had a central test case management tool. Our tests were all created on the fly and stored locally or shared by email. Not surprisingly, our automation efforts always fell short. It&#39;s not necessarily considered best practice to write manual tests and then just automate them but it&#39;s definitely a good start.&lt;br /&gt;&lt;br /&gt;My team just implemented Zephyr, a test case management tool. I&#39;ve barely begun to start using it but at first glance it seems like it&#39;s going to be massively helpful in organizing our test cases and organizing our thoughts into a central repository. Obviously having a new tool won&#39;t solve all of our problems but it&#39;s one more step in the right direction.&lt;br /&gt;&lt;br /&gt;</description><link>http://gettesty.blogspot.com/2013/04/test-case-management.html</link><author>noreply@blogger.com (Yehuda Miller)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6272649600366232306.post-3408627436487652192</guid><pubDate>Thu, 11 Apr 2013 04:04:00 +0000</pubDate><atom:updated>2013-04-11T07:09:55.268+03:00</atom:updated><title>That Moment...</title><description>That moment you realize you have rewrites coming on all your sites...&lt;br /&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;That moment you realize how bad it really is to not have automation in place...&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;That moment you realize that you aren&#39;t alone...&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;I&#39;m here in Toronto attending the first ever STARCanada conference and I&#39;ve been learning so many new, amazing, and innovative techniques for testing, automating, transitioning to agile etc. It&#39;s been great to learn all these things and spend some time learning about things directly related to my job. Because, lets face it, no school teaches testing. There isn&#39;t a college I&#39;ve heard of that offers a bachelors degree in Quality Assurance Analysis.&amp;nbsp;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;However, the best part of this week has been hearing the stories of other testers out there in the trenches. I&#39;ve met junior and senior analysts, managers, consultants, and even bloggers. And I thought to myself, &quot;self, you&#39;ve blogged before. You&#39;ve quite enjoyed it too. Why not blog about QA? About the trials and tribulations of a tester in an agile world?&quot;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;So here I am. That moment when you kick off a blog and hope for the best...&lt;/div&gt;</description><link>http://gettesty.blogspot.com/2013/04/that-moment.html</link><author>noreply@blogger.com (Yehuda Miller)</author><thr:total>1</thr:total></item></channel></rss>