Week 3: “Fixing Performance Problems With Someone Else’s Toolbox”

This week I listened to a live talk, “Fixing Performance Problems Using Someone Else’s Toolbox” by a Java expert.  The title of this video was originally what caught my eye.  As soon as I was about 2 minutes into the video, I was a little apprehensive about finishing it.  He basically was just describing what to do when the tools you depend on to test performance are no longer available.  There are tools like JConsole, Visual VM, and Java Mission Control that people usually depend on for fixing performance problems.  The Java expert talking (not sure why he didn’t say his name?!) told a story about his personal experience with a customer.  The customer went to him and said that the whole system is slow, and it’s taking forever just to login.  When the expert went to use his tools that he relies on to fix performance issues; he realized they weren’t working.  He then started to panic a little bit, but he knew that with the knowledge he had, he could figure this out a different way.  He went on to describe a series of problems that kept getting in the way of his alternative solutions.  There were things like the firewall blocking RMX, JMX not being turned on, and the system not having a X server at all.  Although I am not at all familiar with fixing performance issues, the way he went about everything and his thought process was the reason why I chose to write about this talk this week.

As a future software engineer I need to have the mindset that there is more then one way to fix everything.  When your favorite tool breaks, you need to be able to work around that issue even if it’s not the most efficient and convenient way to do it.  This video opened my eyes to the fact that all of these tools that we are so dependent on, are not by any means the only way to get things done.  We are all so used to doing things the easiest way by using tools to make things a lot quicker..but in reality we don’t NEED them.  An example in just everyday life that I can use to compare this to is, say for example your washer and dryer breaks and you don’t have the money to replace it.  Initially you are going to freak out and think, “Great now I can’t wash my clothes, what am I going to do?”  The reality of it is that you are going to have to find another option, like going to the laundry mat.  I know that may sound terrible and extremely inconvenient to have to drive somewhere just to wash your clothes, but it is possible and it’s not the end of the world.  Engineers need to be able to think logically and think about all of the possible solutions to a problem.  Your original solution may work, but what if a major component of that solution breaks?  As a computer scientist, you need to be able to apply the knowledge that you have when a tool you depend on breaks; both in the computer science world and in everyday life.

From the blog CS@Worcester – Alex's Comp Sci Blog by alexsblog13 and used with permission of the author. All other rights reserved by the author.

System Failure: Importance of Software Testing

You’re a meticulous software developer (or so you thought) who created one of the most useful applications for your country. It’s called the missile detector 1.0 and it’s main function is to alert the appropriate authorities of incoming missiles and the location of where it was shot from. One day, your application detected three missiles incoming from Narnia. Alarmed by such danger, the military shoots 20 missiles to counter attack Narnia. BOOM, a direct hit and now all there is left of Narnia is the memory of it existing one time.

The “three missiles” that was apparently shot from Narnia never made it to your country  so you begin to ponder and ask yourself “what happened?”. Turns out, that there was a bug in your missile detector system that failed to filter out false missile detections caused by sunlight reflecting off cloud tops.

Hakan Kayis wrote an interesting piece on the  Importance of Software Testing. In his article he wrote about many interesting/agreeable reasons as to why software testing is imperative

Here are the highlights

  • Loss of Money
  • Loss of time
  • Damage to business reputation
  • Injury or death

It’s important to test software to work as expected in order to avoid the highlights mentioned above.

Here are some main testing activities that Hakan pointed out:

Testing is not just running tests, but also:

  • Planning and control
  • Choosing test conditions
  • Designing and executing test cases
  • Checking results
  • Evaluating exit criteria
  • Reporting on the testing process and system under test
  • Finalizing or completing closure activities

 

From the blog CS@Worcester – My Blog by justcodeit94 and used with permission of the author. All other rights reserved by the author.

Not Your Dream Job: Video-game Testing (10/7/16)

WIP

 

 

Source: http://www.softwaretestingtricks.com/2014/08/tips-for-becoming-expert-video-game-tester.html

From the blog CS@Worcester – Dan's Tech Rant by danbarbara and used with permission of the author. All other rights reserved by the author.

Priorities

What differentiates good software testers from great?

Priority; the understanding of urgency and ranking of importance. Testers have to evaluate all tasks and adjust accordingly on the daily.

Prioritization can be categorized into three levels being the people level, the process level, and the activity level. At a people level, the tester has more interaction points than potentially anyone on the design team. They have to meet with the business team, the developers, the clients, executives, etc. With a limited amount of time, choosing who to meet with for best interest of the software can be tough. At a process level, consistent testing strategies are good but with more and more end-user expectations there is a need to adapt on the go. For example functional issues are more dependent on the OS rather than screen size. At the activity level, functional testing tends to outweigh non-functional. Testers have to maximize core testing activity.

https://www.stickyminds.com/article/setting-priorities-differentiates-great-testers-rest

From the blog CS@Worcester – Kyle Polewaczyk by kpolewaczyk and used with permission of the author. All other rights reserved by the author.

Reasons why we should love software testing (Week 1)

There are two good reasons to love software testing
the first reason is we can learn quickly. To be a software tester we have to
study the latest trends and understand what the customer are looking to test.
In order to deliver a high-quality service to the customer, we have to do the
studying of the code or the software that they want to test and the reason why.
Every test case can be different from the previous tests so this is a strong
reason to love software testing. We can learn from software testing new things
and become better software developers. The second reason is that we can
implement new ideas. Implementing new ideas is even more critical than studying
new cases of software testing. The generation of new ideas, and being able to
comprehend the big picture can be very challenging for every software developer
but in the end, like I said above these different challenges can make us better
developers, this are the two main reason why we should love software testing.

https://www.utest.com/articles/why-we-love-software-testing

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

Reasons why we should love software testing (Week 1)

There are two good reasons to love software testing
the first reason is we can learn quickly. To be a software tester we have to
study the latest trends and understand what the customer are looking to test.
In order to deliver a high-quality service to the customer, we have to do the
studying of the code or the software that they want to test and the reason why.
Every test case can be different from the previous tests so this is a strong
reason to love software testing. We can learn from software testing new things
and become better software developers. The second reason is that we can
implement new ideas. Implementing new ideas is even more critical than studying
new cases of software testing. The generation of new ideas, and being able to
comprehend the big picture can be very challenging for every software developer
but in the end, like I said above these different challenges can make us better
developers, this are the two main reason why we should love software testing.

https://www.utest.com/articles/why-we-love-software-testing

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

Reasons why we should love software testing (Week 1)

There are two good reasons to love software testing
the first reason is we can learn quickly. To be a software tester we have to
study the latest trends and understand what the customer are looking to test.
In order to deliver a high-quality service to the customer, we have to do the
studying of the code or the software that they want to test and the reason why.
Every test case can be different from the previous tests so this is a strong
reason to love software testing. We can learn from software testing new things
and become better software developers. The second reason is that we can
implement new ideas. Implementing new ideas is even more critical than studying
new cases of software testing. The generation of new ideas, and being able to
comprehend the big picture can be very challenging for every software developer
but in the end, like I said above these different challenges can make us better
developers, this are the two main reason why we should love software testing.

https://www.utest.com/articles/why-we-love-software-testing

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

Reasons why we should love software testing (Week 1)

There are two good reasons to love software testing
the first reason is we can learn quickly. To be a software tester we have to
study the latest trends and understand what the customer are looking to test.
In order to deliver a high-quality service to the customer, we have to do the
studying of the code or the software that they want to test and the reason why.
Every test case can be different from the previous tests so this is a strong
reason to love software testing. We can learn from software testing new things
and become better software developers. The second reason is that we can
implement new ideas. Implementing new ideas is even more critical than studying
new cases of software testing. The generation of new ideas, and being able to
comprehend the big picture can be very challenging for every software developer
but in the end, like I said above these different challenges can make us better
developers, this are the two main reason why we should love software testing.

https://www.utest.com/articles/why-we-love-software-testing

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

Reasons why we should love software testing (Week 1)

There are two good reasons to love software testing
the first reason is we can learn quickly. To be a software tester we have to
study the latest trends and understand what the customer are looking to test.
In order to deliver a high-quality service to the customer, we have to do the
studying of the code or the software that they want to test and the reason why.
Every test case can be different from the previous tests so this is a strong
reason to love software testing. We can learn from software testing new things
and become better software developers. The second reason is that we can
implement new ideas. Implementing new ideas is even more critical than studying
new cases of software testing. The generation of new ideas, and being able to
comprehend the big picture can be very challenging for every software developer
but in the end, like I said above these different challenges can make us better
developers, this are the two main reason why we should love software testing.

https://www.utest.com/articles/why-we-love-software-testing

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

Reasons why we should love software testing (Week 1)

There are two good reasons to love software testing
the first reason is we can learn quickly. To be a software tester we have to
study the latest trends and understand what the customer are looking to test.
In order to deliver a high-quality service to the customer, we have to do the
studying of the code or the software that they want to test and the reason why.
Every test case can be different from the previous tests so this is a strong
reason to love software testing. We can learn from software testing new things
and become better software developers. The second reason is that we can
implement new ideas. Implementing new ideas is even more critical than studying
new cases of software testing. The generation of new ideas, and being able to
comprehend the big picture can be very challenging for every software developer
but in the end, like I said above these different challenges can make us better
developers, this are the two main reason why we should love software testing.

https://www.utest.com/articles/why-we-love-software-testing

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