Ultra Code 2016-10-14 08:11:00

Week-4

Five major problem with software quality testing terms.

Maintaining Good Quality Consistently Over Time – How many oeople maintaining the product quality when they add more people in the team product become more challenging. These difference become more impactful because it is now easy to learn and not easy to teach people to test the function in particular way. To pass the function need to be dedicated efforts from leaderwho share his work with everyone in his team.
Centralized knowledge and Expertise – This kind a problem leader will relate better is that the knowledge and expertise on a perticular testing type get centralized to a few people in a team.
Making Work Fun And Intersting – At your work place make a friendly environment not only with your co-worker and also the people working on the top of your. the people i work with them they all are my friends and we go out for couple of hours to hangout. we also help to eachother work.
Work Distribution/Assignment – this is aanother problem if you are working with a large team or Group it will Distribute / Assignment between all of them. this is the best way to work on the lagre assignment in a small part in that way you can get accurate number and right result.
Appreciation and Motivation – when you work and your supervisor check your work he like it. He apperciate and encourage to give you motivation to do more better in your skills.
The conclusion of this article or i just want to say none of us is as smart as all of us!!!

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-14 08:11:00

Week-4

Five major problem with software quality testing terms.

Maintaining Good Quality Consistently Over Time – How many oeople maintaining the product quality when they add more people in the team product become more challenging. These difference become more impactful because it is now easy to learn and not easy to teach people to test the function in particular way. To pass the function need to be dedicated efforts from leaderwho share his work with everyone in his team.
Centralized knowledge and Expertise – This kind a problem leader will relate better is that the knowledge and expertise on a perticular testing type get centralized to a few people in a team.
Making Work Fun And Intersting – At your work place make a friendly environment not only with your co-worker and also the people working on the top of your. the people i work with them they all are my friends and we go out for couple of hours to hangout. we also help to eachother work.
Work Distribution/Assignment – this is aanother problem if you are working with a large team or Group it will Distribute / Assignment between all of them. this is the best way to work on the lagre assignment in a small part in that way you can get accurate number and right result.
Appreciation and Motivation – when you work and your supervisor check your work he like it. He apperciate and encourage to give you motivation to do more better in your skills.
The conclusion of this article or i just want to say none of us is as smart as all of us!!!

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

Mobile development headaches

Android is great, I think it is a great mobile OS. However, the grievance of developing for it, I have my share of pain. The author complained about Gradle, the build system Google adopted for android, and it can be such a huge annoyance. I have heard people’s project waiting for 4-5 minutes for Gradle to compile.  Every time you change something, it does a full Gradle build. However, this was still an upgrade over what existed before.

I have already written about my annoyance of outdated documentations and poorly documented API’s. Another issue that pops up is during emulator testing. Incompatibility with outdated Google Play Service with the emulator makes it so testing older API versions a pain.  It makes testing apps that need to use the Google Play Service much more difficult.

The author says he’s quitting Android Development, it is not all bad. However, the cons of the Android that IOS seems to have no trouble with, it also has its many pros. The author seems to be more frustrated at Google’s nonchalance at the issues developer face with Android. Apple, being the closed system it is, have its own set of issues. Maybe we should all just switch to Windows Mobile as a protest. (That’ll be the day)

 

One developers good bye to Android:

https://raptureinvenice.com/its-been-real-android-why-im-retiring-from-android/

Further Readings

Should math be prerequisite to programming

https://www.linux.com/blog/should-math-be-prerequisite-programming

Undetectable trapdoors in crypto keys

http://arstechnica.com/security/2016/10/how-the-nsa-could-put-undetectable-trapdoors-in-millions-of-crypto-keys/

Letting your developers concentrate

http://www.geekwire.com/2016/just-shut-let-devs-concentrate-programming-expert-advises/

Amount of deprecation in java over the past 20 years

https://www.azul.com/20-years-java-deprecation/

 

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

Small Amount of Nails, Many Big Holes. (10/14/16)

Have you ever been to one of those batting cages where there is a machine that shoots a baseball straight at you to hit it? Usually it shoots the ball going off based on a timed interval or its continually controlled using some kind of remote control. Imagine this machine in particular is processing based on a timed interval, but the machine secretly had sophisticated AI installed and starts acting on its own pumping out dozens of balls at a fast speed per second. The large amount of balls whip right to you at a certain speed and the only thought you have in your mind is how in the world do you get out of there before getting injured. Usually one would get hit before they manage to move out of the way completely (at least in this scenario), but there is a much more deliberate response to such a situation: focus on hitting the balls that are aiming toward your body with your ninja skills/reflexes and exclude the balls that you know will be far enough to miss hitting you, until the machine runs out of balls that is.

Now in the software testing world, this machine is the software that has been developed for you to test. And the balls that the software is shooting at you, are the bugs. These bugs are within the software are annoying, and most importantly get you in trouble if not reported or dealt with. Bugs can range from software-breaking bugs (the baseballs aiming for your body), or small minor bugs (the baseballs that are no where close to you) that can be over looked. It is up to you (yes you are the only QA guy in the company again), to make sure bugs that are discovered are taken care of in a way where the most important ones are set as high priority and the not so threatening ones to be set in the  “we will get to it whenever we get to it” category. Of course, everything depends on the time you have before the software launches or puts an update out. Getting the best product within the constraints giving to you all depends on you, QA.

tumblr_lzd6aldfmg1qe736z

It’s not that bad really, with a little bit of organizing you can create simple and understanding charts detailing the bugs you found along with given them a label based on threat level and priority. Where you tag a minor bug as level 0 for “eh, whatever” or tagging a more severe as level 5 for “WE GOT A 23-19! WE GOT A 23-19!” Some great ways of prioritizing bugs can be found on Software Testing Stuff’s how to prioritize bugs numerically blog. It’s always a good practice to sort out bugs, let alone will be easier to communicate with the rest of the developer team with easy-to-use charts.

I hope you are good at playing find and seek and know gold from bronze, it shall help you on your quest to prioritize the little insects that need to be squashed.

Source: http://www.softwaretestingstuff.com/2011/09/how-to-prioritize-bugs-numerically.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.

Scrum

Scrum is the idea of working in shorter increments; the idea of planning, attempting to execute that plan, and repeat. With short cycles, teams are relying heavily on automation but what if the test automation sucks?

There are three options in this case,

  • Make it not suck

Make the automation not suck. Put effort into it and make it worthwhile. You’ll spend more time fixing than progressing if a lot of it sucks.

  • Freeze like crazy

The common process is slowing down development to make time for testing then you test, fix, repeat. Since new problems arise from testing, the original problems get frozen in time only to cause more stress down the road upon return. Freezing is essentially gatekeeping as described by Maaret.

  • Do continuous releases with exploratory testing

Begin to think of testing as a manual task just like programing. Test before merging changes into the mainline. More or less: stop doing scrum.

http://visible-quality.blogspot.com/2016/10/the-three-ways-to-solve-our-test.html

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

Regression Testing

This week i chose to write about the article Restest Vs Regression Testing – How much Regression Testers Should be Doing? by Swati S.

The article begins by defining both Retesting and Regression Testing, this was especially helpful since i am new to all forms of Testing.

Retesting was defined simply as testing again, “the reason does not matter(Swati 1)”. The reason could be as simple as you were not paying attention the first time that the test was run.

Regression Testing is a little bit more complicated. The article gave an example that i believe beautifully illustrates it’s function. “Imagine yourself making a block tower, by adding one block over the other. You don’t take the time to reinforce or strengthen the base. It won’t be long before the tower crashes, isn’t it?(Swati 1)”. It is based on the idea that software continues to grow and as you continue to release updates it is important to go back and test the base of your software to make sure it is still stable. This is a version of retesting, the only thing is that there is a specific reason this time. The reason being to make sure updates to the software have not made any “before working functionality unstable”.

Before a Regression Testing is implemented it is important to do a “Regression Analysis” in order to understand how much testing needs to be done. This is something that is application specific, depending on what is being updated perhaps you do not need to test all the way back to the bottom block but only half way down. According to the article there are three important factors when doing a “Regression Analysis’:

  • “Nature of the change”
  • “Relationship/impact of the change on the current system/feature”
  • “Availability time and resources”

Based on those above factors and the decisions that the developers make they can do a few different types of regression tests:

  • Unit Regression – Only test the area of the application that has been modified.
  • Partial Regression – Test the are of the application that has been modified and all those areas that interact with that area.
  • Full Regression – Retest the entire application regardless of where the actual change was done.

Essentially the difference between the two types of testing is that Regression Testing is only implemented when there is a change to the application. Yes it is a version or Retesting but it is different. Retesting can be done without a change, for any reason the developer sees necessary.

Here are some other articles that i found interesting:

Faster Websites with WebPageTest

http://www.mkltesthead.com/2016/10/the-humans-in-machine-talking-machine.html

Automated UI Testing for iOS and Android Mobile Apps

https://www.stickyminds.com/better-software-magazine-article/evolution-software-monetization


From the blog CS@Worcester – Computer Science Journal by jtassone93 and used with permission of the author. All other rights reserved by the author.

SnapIt

Michael Larsen wrote an interesting piece about a new feature from the LoseIt iPhone app called SnapIt. During the weekend of October 7th, he hosted a testing Americas session where he and Anna Royzman had tested the new feature in the app. The new feature allows you to take a picture of the food item, displays what the app thinks it is, and gets the macronutrient breakdown.

When it came down to testing, there were a few bugs with the feature. The feature did not do well when it came down to taking pictures of complex and packaged foods. When they took a picture of a walnut, the suggested food items that came up were Gnocchi, Chicken, and Ravioli all of which are not related to any kind of nuts. There was another interesting bug discovered when they were doing their testing. When the user takes two pictures and then discard them, on the 3rd try of picture taking, the bottom of the camera button disappears only showing the top half of the camera button. In order to fix this, they had to close the app and open it back up again.

I think this feature is brilliant if they fixed all of the bugs found and had a more accurate reading on the food item, because I know a lot of gym goers that track their macros on a daily basis. Instead of having to go through the hassle of looking it up online or having to read the very small print on the back, users of the app can just take a picture of it.

Read more about it here

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

The Key to INFINITE Testing!

Okay…I might have exaggerated the title a little bit. When I say infinite testing I really mean continuous testing, which in really broad context pretty much means the same thing (that is, if the continuous testing goes on forever).

Since we are currently learning about different testing methods and techniques in our Software Testing and Assurance course, an article about continuous testing peaked my interest. As technology continues to evolve so does our software, which is why it is important to keep up to date with testing to ensure that our programs are bug-free. The article on rainforestqa.com (https://www.rainforestqa.com/blog/2016-10-11-when-does-continuous-testing-happen/) goes into details about which stages continuous testing plays a crucial role in. The objective of continuous testing is  to publish your code to customers as fast as possible with high quality releases which is achieved using several different testing methods, such as unit testing, automation testing, and manual testing.

Like almost every other program, continuous testing should start at the beginning of development and carry out throughout production. During the stage of development, unit testing is the primary use to debug and catch errors. Some companies even use test-driven development strategies where writing test code is placed before writing the program code. Once it hits the stage of production, it starts to become easier because at this point the test cases should already be fairly stabilized so automation testing is primarily used during this stage since only small feature changes are being made. Although automation test is commonly used, some companies recommend “smoke and sanity” tests as well which are tests that are manually ran to test the integrity of the core program flow to ensure everything is working properly.

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.

What Classes Should Be Tested

Testing on the Toilet: Prefer Testing Public APIs Over Implementation-Detail Classes

In this blog post by Andrew Trenk, Trenk goes over what code needs to be tested, and what doesn’t, when making a Public API. Trenk goes on to explain that if a simple piece of code has only one user or is used once in another class, you should create tests for the other class or not bother testing the simple code at all. He says that anything that is an implementation detail should not get it’s own test.
In fact if you do create tests for this implementation, it might make the code and tests harder to maintain over time, it could cause issues when trying to refactor, and it could also hide issues in your code that only show when using the API. Overall Trenk suggests testing your implementation details indirectly through your API classes. This way you see that they work with your API and you have fewer tests that will need to be updated.

From the blog CS WSU – Techni-Cat by clamberthutchinson and used with permission of the author. All other rights reserved by the author.

Black-Box, Grey-Box, White-Box (Week 2)

10/11/2016
Three important concepts in software testing: black-box, grey-box and white box and manual tests methods.
When tester doesn’t have access to the code and the code is executable this type of testing is called black-box testing. Here is a manual test method example, when we install an application into a device then we create the test case based on requirement and then execute the test in order to verify the expected required output.
When a tester has access to a partial source of code is called gray-box testing . An example of manual gray-box testing : When a tester manually input all parameters into SDK’s API and then manually check the output for the expected required results.
When a tester has full access to all the source code is called white-box testing. An example of manual white-box testing : When a tester checks the compiler  error warning or use static code analysis tool , check for null dereference, context leak, and resource leak.
All the examples that I provided above can be part of our future career and are very important to know the difference between the Black-box, grey-box, and white-box.
Source
https://www.utest.com/articles/examples-of-black-box-grey-box-and-white-box-testing

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