For this blog i chose the podcast Making a better tester with Keith Klain from the testinginthepub podcast website. This is a website where there discuss various topics in the software testing field. I picked this podcast because it sounded interesting and seemed like a good starting point into the world of software testing. It discusses some of the downfalls in the testing field and areas to improve as well as an overview of the state of the industry today.

The podcasts starts with the guest of the show Keith Klain discussing one issue that seems to come up a lot in the testing field. This was that the testing teams objectives would not align well with the business side. He talks a lot about how often times when he consults for a company he will see that the testing team is effective, but simply that their goals to not match that of their business counterparts. He then goes on to state how important it is for the testing team to have good communication skills with the business team and to have their goals aligned to make testing as effective as possible.

The next section of the podcast builds where the previous section left off. This section talks about how one of the big things holding the industry back is that a lot of company’s still use very old ways of handling their testing. Most of this includes outsourcing all of their testing to independent firms and testing centers. Keith Klain states that as much as fifty percent of major financial firms and banks still outsource all their testing to large testing centers in other countries. This not only makes it harder to communicate and have everyone on the same page but also since this company’s treat this as an external service and  just get the results back they do not truly understand the data that they get from testing. The podcast also discusses that financial aspect of it ,stating that it is hard to completely phase these practices out because they are so deeply ingrained and these testing centers make a lot of money and employee a large number of people. Keith Klain also states that the reason a lot of these company’s are having a hard time updating their systems to agile or waterfall development is because of how heavily they rely on these large testing centers.

The last section of the podcast talks about the exposure and communication in the testing community. The podcast refers to a recent expo that the hosts had attended which was not testing expo but a more general tech expo. The podcast talks about how a lot of people seem the have misconceptions about what testers are and really do.Keith Klain talks about how the testing community needs to be a little more social in order to draw new people into the community.To finish up the podcast Keith Klain talks about the usefulness of experience reports and documenting some of the experiences you have in your testing job , and how this can be really helpful for figuring out which systems work in different contexts.

In conclusion i found this article to be very interesting and gave a good insight on where the industry is today and where it is going. To me it seemed to be plagued by a lot of the same issues as in other parts of tech, such as technology moving very fast and a lot of non tech companies having trouble keeping up. It also seems like the industry is held up by a lot of old infrastructure that is hard to remove because the amount of money that is tied up, which i would also say is a larger problem in the tech industry. One thing that interests me is seeing how the industry will grow, will the testing teams start working much closer with the development teams and how will this effect performance. If so will we then see a shift into developers writing their own tests and having the whole process be that much more unified, and if so how will this effect performance and the industry.There is a part 2 of the podcast which i am looking forward to listening to.

-Thank you for reading






Week 5

This week i started looking at the ticket TRUNK -248 with my group. the ticket is dealing with going through the to-do’s and finding where the to-dos are asking for a Junit test. First i did a bit of research on junit tests so i could some background. After a quick google search i went to http://www.vogella.com/tutorials/JUnit/article.html which was a great in depth article on Junit. i didn’t focus on the using aspects too much since that’s not what my ticket is asking for however it did explain how the tests work and what too search for in the source code to track some of these down. After that i went to https://wiki.openmrs.org/display/docs/Step+by+Step+Installation+for+Developers which helped me setup the openmrs core in eclipse. I had to go to help marketplace and get a plugin for maven on eclipse. after installing the maven plugin i went to file import then chose import and then existing maven project and chose the core repo that i cloned from github. After the import finished which took a couple of minutes i finally had access to the OpenMRS source code. I started looking through some of the code and identifying some of the todo items that ask for junit tests. I wasnt sure if the ticket was still active or not but i did find a bunch of to-do items asking for junit tests so it seems like it still is. This following week me and my group hope to identify as many of these as possible to we can accomplish our ticket.

Week 4

The install went through for me almost without a hitch, i ran the OpenMRS SDK like it said which installed without a problem. After it installed i tried the omrs-version command in the command prompt to check if it had installed successfully. At first it said “Error: JAVA_HOME not found in your environment. Please set the JAVA_HOME variable in your environment to match the location of your Java Installation” after a quick Google search i did the command “set JAVA_HOME=c:\Program Files\Java\jdk1.7.0_45” i did the omrs-version command again and everything seemed to be in working order like it showed in the developers guide. Besides that i had no other problems with the installation.

Week 3

The wiki editing stuff that we did this week all seemed to be pretty straight forward, its not the hardest thing in the world to edit a wiki but i could see it getting annoying at times. The issue tracker activity was a good way to get a bit more familiar with the open mrs issue tracker. the definitions were easy to figure out just by reading some of the description on the site and just by browsing the site. Although the definitions were easy to find it forced you to use all the parts of the issue tracker which is a good way to get really comfortable with it. The GIT tutorials and homework was much like what we had done in class, it just shows how to use GIT and get more comfortable with it since it is a tool we will be using a lot. They were alright for the most part nothing ground breaking but good references if you get stuck somewhere which did seem to happen to me a few times.

I picked 3 introductory tickets that to me seemed like they could be accomplished, i tried to pick tickets that were not too hard since part of the problem at first is gonna be getting comfortable with the whole process that comes along with fixing an issue.


Week 2

The class that we had in irc was different to say the least. At first the silence was really weird for me but after a little bit of time in irc the conversations seemed to flow well and the class seemed to become quite normal, if anything with a little less clutter since everyone’s points are written out and become much easier to track. I thought the readings were quite interesting, i wave worked doing some it support in the past were they really focused on their ticketing system and good documentation. I was happy to see that some of these same things are used in open source development since it is something i feel i can do very well. I also like the part on the life cycle of the bug tracker i didn’t realize there were so many steps to be taken before the problem is even addressed.

Week 1

This class seems like it is going to be a lot different then some of the Computer Science classes that i have taken in the past. Up to now i feel like we have been doing just a lot of busy work type programming nothing that i feel is actually too practical. I think it will be very interesting to work on something a lot larger and more practical then in the past. I am also interested to see how the open source aspect will play out.

I feel like a lot of the ideas in The Cathedral and the Bazaar where things i was already familiar with but it was still a very informative article. Seeing the author first getting into this open source project and him starting to see all of the benefits of open source programming really helps reinforce some ideas that i was already familiar with.

The free vs. open article although interesting was not something that i particularly worry about.  The only difference that i could really see was that in some cases software under Open source initiative might have restrictions on who can release the executable version however the source code is still available. I see that free is more of an ideology versus open which is more about just getting a better piece of software but at the end of the day for me the differences are not really big enough to concern me.

I really liked reading the OpenMRS developers guide because it gave some background to what where going to be working on. Seems like the project is for a good cause and beneficial to many. The project is also very large containing 40 thousand lines of code and being used in many parts of the world. These things all seem very exciting and i am looking forward to working on this project

I haven’t used too much of Git or Irc however i did get both setup and working. I am interested in seeing how these things work more closely since both seem like great tools for making your life as a programmer and especially as programmer that’s part of a team much easier.