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.

Mobile App Testing

Cellphones are widely used today as a form of communication among different groups of people. However, nowadays that is not the only primary function of a cellphone. The other primary use for a cellphone is entertainment, and with that comes mobile apps. I came across an article this week titled “4 Methods for Mobile App Testing that Emulate Real-World Use Cases”.(link: https://www.rainforestqa.com/blog/2016-08-29-4-methods-for-mobile-app-testing-real-world-use-cases/) which talked about how different types of testing can be applied to detect defects in common everyday mobile applications.

Out of the 4 methods the article touches base on, I found the third method to be particularly interesting because it was one I had never thought of before and I found it to be a useful tool. The testing method was to “Dog food your own product”. This meant to incorporate the application and use it with your everyday life. Since you are the creator / programmer you understand how you want the application to perform and behave so you can detect issues or bugs within the program once you encounter them. Besides that, since you are incorporating it as a part of your daily activities, you are more likely to come across problems that might not have been thought of during the testing process. I found this method to not only be fascinating but also beneficial because it could also potentially exploit detailed flaws like device type, battery life and other environmental factors that may have not been considered.

From the blog CS@Worcester – Tan Trieu's Blog by tanminhtrieu and used with permission of the author. All other rights reserved by the author.

To Test it All

As I learn more about Software development and testing, I’ve come to find that 100% testing a major software system is very difficult. Earlier this week I read a blog post from Saucelabs (you can read it here) that covered the topic of code coverage vs. available resources. The main focus of this blog post was not worrying about testing 100% of the software system but testing it smartly.

The writer looked at a few different ways to approach testing smartly. One of the ways was by looking at what the “typical” user input was. I found this interesting because it makes total sense. Instead of testing for every thing you might expect the user to input. Thoroughly test the most common things you expect the user to input.

The next way the writier looked at with testing smarter is the Pareto Principle. This principle simply states that 20% of your inputs should result you in 80% gains. So in testing that translates to for 20% of your tests you should find 80% of your bugs. This is quite an interesting topic and intuitive when you think about it. 20% of your tests should cover everything you can easily think of that could be an issue. That leaves 80% of your tests and time to be able to worry about the many edge cases that effect a software system.

The last way the writer looked at approaching software smartly was by using big data. Using big data we are able to look at trends of what the user is using for supporting hardware or software and what types of things the users are clicking and using more often. That way you are able to focus your efforts on the more important aspects of your software system.

From the blog CS@Worcester – Tyler Lundstrom by CS@Worcester – Tyler Lundstrom and used with permission of the author. All other rights reserved by the author.

When is Testing Over?

Testing can sometimes never be fully completed, so software is released that may contain bugs. If every software was completely 100% tested it might never get released. The two easy ways to know testing is over is if the deadline is met or the budget is exhausted. The test coverage should be 95% passing, and the test coverage should be at least 95%. All major defects should be fixed so the 5% failing tests should be small defects.

Knowing when testing is over can be hard, but these few tips helped me learn when to stop.

When to Stop Testing (Exit Criteria in Software Testing)


From the blog CS@Worcester – Software Testing by kyleottblog and used with permission of the author. All other rights reserved by the author.

Hi Everybody! I am so happy that you chose to visit my site!

Hello visitor,

This is my first post! I am a computer science junkie and I’ll be posting the fascinating things I learn related to my field.

I love hearing your opinions and thoughts on my posts. So please leave a comment below!

Buvaneshwaran T

From the blog CS@Worcester – thewisedevloper by thewisedeveloper and used with permission of the author. All other rights reserved by the author.