Week 5 – 6 Tips For Making Time to Test

Here are 6 tips to make sure that you have enough time to properly test your code as provided by Swati S. in her blog What To Do When There Isn’t Enough Time To Test.

  1. ESTIMATE ACCURATELY – Overestimate the amount of time each step is going to take.  Do not forget to take into account your team, tools, and processes.
  2. HISTORICAL DATA – Swati suggests asking the following questions:
  • How long did the earlier release test cycles take?
  • What kind of issues caused interruptions to the previous test cycle?
  • How many runs did most test cases take before they passed?
  • What defects were reported?
  • What defects caused the testing to be interrupted?

3. ASK THESE QUESTIONS – Swati suggests asking the following questions:

  • Find out Important functionality is your project?
  • Find out High-risk module of the project?
  • Which functionality is most visible to the user?
  • Which functionality has the largest safety impact?
  • Which functionality has the largest financial impact on users?
  • Which aspects of the application are most important to the customer?
  • Which parts of the code are most complex, and thus most subject to errors?
  • Which parts of the application were developed in rush or panic mode?
  • What do the developers think are the highest-risk aspects of the application?
  • What kinds of problems would cause the worst publicity?
  • What kinds of problems would cause the most customer service complaints?
  • What kinds of tests could easily cover multiple functionalities?

4. USE A TEST MANAGEMENT TOOL – This will reduce the amount of time testing takes             at every stage of the process.

5. DON’T REINVENT THE WHEEL – Make sure to look at the Unit test results to                            determine whether or not the build was a success and to see which tests failed.                        Reviewing the results will ensure that the same errors are not repeated.

6. MEASURE YOUR PRODUCTIVITY – Pay attention to the goals that you set and make                sure they are obtained.  If your goals are not being achieved, reevaluate the time                      allotted for those goals.  Consequently, if you are achieving goals at an accelerated                  rate, reevaluate the time allotted for those goals.

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

Posted in CS443 | Comments Off on Week 5 – 6 Tips For Making Time to Test

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.

Posted in CS443 | Comments Off on Week 4 – Criteria For Picking An IDE

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





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

Posted in CS@Worcester | Comments Off on TestLink(Week 5)

Week 3 – When To Stop Testing


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.

Posted in CS443 | Comments Off on Week 3 – When To Stop Testing

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



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)?
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 Alex Gupta and used with permission of the author. All other rights reserved by the author.

Posted in CS@Worcester | Comments Off on Ultra Code 2016-10-21 00:04:00

Week 2 – An Inside Look At Testing

Yes, I know, Brendan Connolly again.  Out of the ten blogs I have gone through so far, his are the only ones that I have continued to read until the end.  His blogs are straight to the point and that keeps my attention.  Anyway, onto the blog.

First of all, let’s take a broad look at the purpose of testing.  In a very general sense, we test to reveal problems. Then those problems are reported so that they can be resolved. In his blog, Connolly asserts that, “A tester needs a clear understanding of what a problem is in their context in order to effectively relay their findings to stakeholders.” He relates the his model to the Scientific Method, so even if you don’t know much about testing, you can get a grasp on the idea behind it.

Connolly suggests a good way to grasp testing is to have groups of two working together, with one person as the tester, and the other as an observer.  The key for this to work is verbalization.  The tester needs to relay to the observer the actions he is taking and the thought behind his actions.  The observer is not silent, he must be paying attention, adding his or her input, and watching for bugs.  The important factors the tester and observer must agreed upon are the coverage of the project and the tempo at which the individuals work.

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

Posted in CS443 | Comments Off on Week 2 – An Inside Look At Testing

How can SQL help your testing abilities? (Week 5)

The reports that SQL can generate transforms raw information into useful data also can be used as a tool that can help to refine your testing abilities. The methods that SQL provide can help perfect the skills of programmers. The methods help to get correct results  when we testing back-end applications.SQL is a parent-child relationship schema that allows information to be accessible and allows to minimize discrepancies across data which create reliable output tables.The tables with columns and rows that build up the records of employment can help the End user have a interactive graphical Interface. The interactive graphical interface it can help the users to make changes. SQL is used in a variety of testing tools; the tools that are used mostly to select information that is relevant and can provide insight into the business practices. Some of the automation tools that is used to create a quality product are QTP and Selenium. QTP provides functional test automation for software applications and environments and Selenium is a free (open source) automated testing suite, Selenium is used to test web applications. Both tools use different languages QTP  run on Java and Selenium runs on VBscript. There are some global statements that are used from SQL one of the statements is the sorted procedure. The advantage of Sorted procedure is that it can minimize work and it can decrise the amount of time it requires for testing by preventing reniventing the wheel. SQL have more capabilities available, which makes it helpful tool when we have to verify data.If we use these methods we can get better testing results.

From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.

Posted in CS@Worcester, Software Testing | Comments Off on How can SQL help your testing abilities? (Week 5)