Week 4 – Criteria For Picking An IDE

Although this blog is very loosely associated with testing, I still think it is important enough to warrant my attention. In his blog, Erik Dietrich outlines a list of criteria for “what is reasonable to expect from your IDE.”

  1. BUILDING THE SOFTWARE – His first criteria is that the IDE should be able to easily build your software. Additionally, the IDE should alert you of any problems and make it easy for you to locate those problems.  Ideally, the IDE would even suggest solutions to those problems.
  2. INTEGRATED DEBUGGER – Another essential aspect for an IDE is an integrated debugger.  The debugger should allow you to go through your code line by line and see the behavior of your code at runtime.
  3. PLUGINS AND CUSTOMIZATION – Any effective IDE or text editor relies on plugins.  Plugins and customization make you more productive and enhance the the coding experience.
  4. AUTOMATED REFACTORING – Here is the aspect that relates this blog to software testing.  Dietrich explains that he is a huge proponent of TDD.  A major factor in TDD is refactoring, and he suggests that an IDE that automates refactoring removes much more human error from the TDD process.  Not only does it remove error, but it is also much more efficient.
  5. INTELLISENSE/NAVIGATION – The last criteria is pretty self-explanatory.  An IDE should make navigating your code easy, and offer type-ahead support.

From the blog cs443 – TayNock's Blog by taynock and used with permission of the author. All other rights reserved by the author.

TestLink(Week 5)

Test link is a web based open source test managment tool. It integrates both requiremtns specification and test specification together. It also supports buoth manual and automated execution of test cases. It supposted test reports in MS word, Excel, and html formats.

There are many benefits that come with TestLink. First it supports multiple projects, so you can work on multiple different projects at the same time. It is easy to import and export test cases. You can also filter test cases with keywords, so it is easy to find a particular test. Also, testlink can provide credentials to multiple users and assign roles to them, and you can assign test cases to multiple users.

This test management tool is different than the ones we use in class. SInce this is a Web based tool, multiple users can use it at the same time if they log in with their credentials that Test Link provided for them.

A Layman’s Guide to TestLink Test Management Tool – TestLink Tutorial #1

 

Other blogs i looked at

https://testing.googleblog.com/2016/10/hackable-projects-pillar-2-debuggability.html

https://testing.googleblog.com/2016/09/what-test-engineers-do-at-google.html

https://testing.googleblog.com/2016/06/the-inquiry-method-for-test-planning.html

https://testing.googleblog.com/2016/03/from-qa-to-engineering-productivity.html


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

Week 3 – When To Stop Testing

19397645-smiley-with-stop-sign-vector-illustration-stock-vector

Before you start. KIDDING. Alright so for this week’s blog I’m mixing it up and recapping a blog I read on softwaretestinghelp.com written by Renuka K.  This blog can be found here.

Well Renuka paints the picture of the typical tester.  Enthusiastic at the start and losing fervor with every run through the code.  Which makes sense, the more times a tester looks through the same code, the less interested that tester is going to be in that code. Especially because, if the testing is done correctly, the tester will find less defects with every run.  So then the question is, when is it okay for the tester to stop?

In the first scenario, for discontinuing testing, Renuka broaches the idea that a tester can stop testing when all of the defects have been found.  Unfortunately, there is no way to prove that software is free of bugs.

In the next scenario, Renuka suggests exit criteria, including, time, budget, and extent of testing.  Unfortunately, as Renuka points out, the quality of the testing process is compromised when these constraints are applied.  Before testing begins, conditions to be fulfilled should be established in order to conclude testing.

Below is  a useful yes or no list Renuka provided to help you decide if it is time to stop testing:

  • Are all test cases executed at least once?
  • Is the Test Case Pass rate as defined?
  • Is complete test coverage achieved?
  • Are all functional / Business flows executed at least once?
  • Is the decided defect count reached?
  • Are all Major High Priority Defects fixed and closed?
  • Have all Defects been Retested and closed?
  • Has Regression been done for all open defects?
  • Have you exhausted the testing budget?
  • Has the Testing end time reached?
  • Are all Test Deliverables reviewed and published?

 

From the blog cs443 – TayNock's Blog by taynock and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-10-21 00:04:00

Ankit
Week-5

Question

Due to the success of the Watch an Expert series, I was thinking about possibly setting up a bug battle competition in the future, with the ability for uTesters to watch live. I was envisioning it sort of as an eSport, with anywhere from 2-4 testers competing to see who can find the most valuable bugs in a certain amount of time. Although I think this would be a really exciting event, at the same time I’m struggling with whether software testing naturally lends itself to a tournament format. Does anyone think this would be a good idea? Bad idea? Any suggestions on what the rules/entry requirements/judging criteria would be? Anyone interested in participating (assuming it takes place)?
Suggestion:
I really like this idea, and am just going to write out loud for a moment about what I envisioned upon reading your post. Please note that I don’t really watch or follow eSport tournaments, so my thoughts might be slightly ill-informed, unrealistic, or just plain bad.When I looked for more information on uTest’s previous contests I found this. Unfortunately, many of the links I wanted to click on that branch from that article result in 404s. Have the previous bug battles on uTest been popular? If so, what aspects of the competition did the testers/audience find most appealing? 
I wonder how team dynamics would factor into generating interest for the tester audience. Since testing is (more or less) a solitary effort, what would motivate me to watch Tag-Team Testing? What’s the primary value added reason for watching?

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-10-21 00:04:00

Ankit
Week-5

Question

Due to the success of the Watch an Expert series, I was thinking about possibly setting up a bug battle competition in the future, with the ability for uTesters to watch live. I was envisioning it sort of as an eSport, with anywhere from 2-4 testers competing to see who can find the most valuable bugs in a certain amount of time. Although I think this would be a really exciting event, at the same time I’m struggling with whether software testing naturally lends itself to a tournament format. Does anyone think this would be a good idea? Bad idea? Any suggestions on what the rules/entry requirements/judging criteria would be? Anyone interested in participating (assuming it takes place)?
Suggestion:
I really like this idea, and am just going to write out loud for a moment about what I envisioned upon reading your post. Please note that I don’t really watch or follow eSport tournaments, so my thoughts might be slightly ill-informed, unrealistic, or just plain bad.When I looked for more information on uTest’s previous contests I found this. Unfortunately, many of the links I wanted to click on that branch from that article result in 404s. Have the previous bug battles on uTest been popular? If so, what aspects of the competition did the testers/audience find most appealing? 
I wonder how team dynamics would factor into generating interest for the tester audience. Since testing is (more or less) a solitary effort, what would motivate me to watch Tag-Team Testing? What’s the primary value added reason for watching?

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-10-21 00:04:00

Ankit
Week-5

Question

Due to the success of the Watch an Expert series, I was thinking about possibly setting up a bug battle competition in the future, with the ability for uTesters to watch live. I was envisioning it sort of as an eSport, with anywhere from 2-4 testers competing to see who can find the most valuable bugs in a certain amount of time. Although I think this would be a really exciting event, at the same time I’m struggling with whether software testing naturally lends itself to a tournament format. Does anyone think this would be a good idea? Bad idea? Any suggestions on what the rules/entry requirements/judging criteria would be? Anyone interested in participating (assuming it takes place)?
Suggestion:
I really like this idea, and am just going to write out loud for a moment about what I envisioned upon reading your post. Please note that I don’t really watch or follow eSport tournaments, so my thoughts might be slightly ill-informed, unrealistic, or just plain bad.When I looked for more information on uTest’s previous contests I found this. Unfortunately, many of the links I wanted to click on that branch from that article result in 404s. Have the previous bug battles on uTest been popular? If so, what aspects of the competition did the testers/audience find most appealing? 
I wonder how team dynamics would factor into generating interest for the tester audience. Since testing is (more or less) a solitary effort, what would motivate me to watch Tag-Team Testing? What’s the primary value added reason for watching?

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-10-21 00:04:00

Ankit
Week-5

Question

Due to the success of the Watch an Expert series, I was thinking about possibly setting up a bug battle competition in the future, with the ability for uTesters to watch live. I was envisioning it sort of as an eSport, with anywhere from 2-4 testers competing to see who can find the most valuable bugs in a certain amount of time. Although I think this would be a really exciting event, at the same time I’m struggling with whether software testing naturally lends itself to a tournament format. Does anyone think this would be a good idea? Bad idea? Any suggestions on what the rules/entry requirements/judging criteria would be? Anyone interested in participating (assuming it takes place)?
Suggestion:
I really like this idea, and am just going to write out loud for a moment about what I envisioned upon reading your post. Please note that I don’t really watch or follow eSport tournaments, so my thoughts might be slightly ill-informed, unrealistic, or just plain bad.When I looked for more information on uTest’s previous contests I found this. Unfortunately, many of the links I wanted to click on that branch from that article result in 404s. Have the previous bug battles on uTest been popular? If so, what aspects of the competition did the testers/audience find most appealing? 
I wonder how team dynamics would factor into generating interest for the tester audience. Since testing is (more or less) a solitary effort, what would motivate me to watch Tag-Team Testing? What’s the primary value added reason for watching?

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-10-21 00:04:00

Ankit
Week-5

Question

Due to the success of the Watch an Expert series, I was thinking about possibly setting up a bug battle competition in the future, with the ability for uTesters to watch live. I was envisioning it sort of as an eSport, with anywhere from 2-4 testers competing to see who can find the most valuable bugs in a certain amount of time. Although I think this would be a really exciting event, at the same time I’m struggling with whether software testing naturally lends itself to a tournament format. Does anyone think this would be a good idea? Bad idea? Any suggestions on what the rules/entry requirements/judging criteria would be? Anyone interested in participating (assuming it takes place)?
Suggestion:
I really like this idea, and am just going to write out loud for a moment about what I envisioned upon reading your post. Please note that I don’t really watch or follow eSport tournaments, so my thoughts might be slightly ill-informed, unrealistic, or just plain bad.When I looked for more information on uTest’s previous contests I found this. Unfortunately, many of the links I wanted to click on that branch from that article result in 404s. Have the previous bug battles on uTest been popular? If so, what aspects of the competition did the testers/audience find most appealing? 
I wonder how team dynamics would factor into generating interest for the tester audience. Since testing is (more or less) a solitary effort, what would motivate me to watch Tag-Team Testing? What’s the primary value added reason for watching?

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-10-21 00:04:00

Ankit
Week-5

Question

Due to the success of the Watch an Expert series, I was thinking about possibly setting up a bug battle competition in the future, with the ability for uTesters to watch live. I was envisioning it sort of as an eSport, with anywhere from 2-4 testers competing to see who can find the most valuable bugs in a certain amount of time. Although I think this would be a really exciting event, at the same time I’m struggling with whether software testing naturally lends itself to a tournament format. Does anyone think this would be a good idea? Bad idea? Any suggestions on what the rules/entry requirements/judging criteria would be? Anyone interested in participating (assuming it takes place)?
Suggestion:
I really like this idea, and am just going to write out loud for a moment about what I envisioned upon reading your post. Please note that I don’t really watch or follow eSport tournaments, so my thoughts might be slightly ill-informed, unrealistic, or just plain bad.When I looked for more information on uTest’s previous contests I found this. Unfortunately, many of the links I wanted to click on that branch from that article result in 404s. Have the previous bug battles on uTest been popular? If so, what aspects of the competition did the testers/audience find most appealing? 
I wonder how team dynamics would factor into generating interest for the tester audience. Since testing is (more or less) a solitary effort, what would motivate me to watch Tag-Team Testing? What’s the primary value added reason for watching?

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-10-21 00:04:00

Ankit
Week-5

Question

Due to the success of the Watch an Expert series, I was thinking about possibly setting up a bug battle competition in the future, with the ability for uTesters to watch live. I was envisioning it sort of as an eSport, with anywhere from 2-4 testers competing to see who can find the most valuable bugs in a certain amount of time. Although I think this would be a really exciting event, at the same time I’m struggling with whether software testing naturally lends itself to a tournament format. Does anyone think this would be a good idea? Bad idea? Any suggestions on what the rules/entry requirements/judging criteria would be? Anyone interested in participating (assuming it takes place)?
Suggestion:
I really like this idea, and am just going to write out loud for a moment about what I envisioned upon reading your post. Please note that I don’t really watch or follow eSport tournaments, so my thoughts might be slightly ill-informed, unrealistic, or just plain bad.When I looked for more information on uTest’s previous contests I found this. Unfortunately, many of the links I wanted to click on that branch from that article result in 404s. Have the previous bug battles on uTest been popular? If so, what aspects of the competition did the testers/audience find most appealing? 
I wonder how team dynamics would factor into generating interest for the tester audience. Since testing is (more or less) a solitary effort, what would motivate me to watch Tag-Team Testing? What’s the primary value added reason for watching?

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.