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.

Accepting Acceptance Testing

Searching through blogs  I came across a post about acceptance testing. This stood out to me because I had not heard of it so I thought I would find out what it is and make a post about it.

The full name is User Acceptance Testing. This type of testing is a step in development after unit system testing where you find out if the product will be accepted by the customer and if it is ready for release. This seems kind of obvious but it is one of the more important types of testing to make your customers happy.

The official definition in the International Software Testing Qualification Board Glossary is Acceptance Testing: Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to determine whether or not to accept the system.

Most video gamers know that there is a recent trend in video games that allows players to get early access to the game. Or known as Alpha or Beta. I mention this because this is one kind of Acceptance testing known as Internal Acceptance testing and external Acceptance testing.

More information can be found here or here.

From the blog CS@Worcester – Conundrums In Computing by patrickgrahamblog and used with permission of the author. All other rights reserved by the author.

Problems with Acceptance Testing

As a student I am not familiar with acceptance testing mostly because it involves a client. With acceptance testing, the program is given to the business or client and the client makes sure all of their specifications were met. This is done throughout the development process, not just once the program is complete.

This is a great way to test but there are some issues. One of the biggest ones is communication, because the program is handed off from the client to the tester to the developer, not specifically in that order, communication is often lost. All three often do not work together but just pass off code or specifications. Another issue is exposure of the program to the client. This can lead to the client thinking they know how to fix issues or how to develop code. There should be a clear line that the client should stick to their business and the developers do their jobs.

After learning about acceptance testing these are only a couple of the many issues out there, but I thought they were some of the most important.

http://www.softwaretestingmagazine.com/knowledge/problems-acceptance-testing-can-cause/

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

All Music No Ears

An article I read about the iPhone 7 and how its changing showed me a new level of depth of their thoughts. Why would a company as such as APPLE take out the auxiliary port of the new model of the iPhone? A very controversial decision that was despised by almost all of its user base,  alienating everyone who uses their iPhones to play music at parties or in the car, which is mainly how the popularity of the iPhone even first came to be. Now taking this as a huge risk, I’ve realized that soon enough, it had to be taken. Big companies such as Apple, who are trying to trump all other businesses in their lane to cause a monopoly and want/need to show their power and their hardware being unique to their products. For innovation to move forward, users need to be put in a place of discomfort. Apple is choosing to take itself away from other companies by making hardware changes that are most easily accessible to its own products. Doing what no one else is, a brand’s success can come from its differentiation from all the other brands. As their faithful fan base chooses to stay with them, a jackless iphone will eventually become the new normal for the iphone, making its design stand out and lead innovations over other hardware that fades away into its design which is very similar to everything else. Because this transition can be bumpy, to optimize the pain and help people make the process faster rather than be painful over time, they did it in one swift model change because you can’t slowly get rid of a headphone jack.

From the blog CS@worcester – CS Blog by Gautam by csblogbyg and used with permission of the author. All other rights reserved by the author.

Expensive Come Up

This article I read about outsourcing talked about our world evolving. As our society gets more developed, and more and more engulfed in technology, programmers are becoming more expensive. As you try to get your company off the ground, you might not even be able to afford it because your developers are commanding such high salaries. So one of the large ways to help your situation would be to outsource your developers. Since affording a whole team of project managers to maintain a high quality would be too much, hiring remote developers in a different place in the world is not only cheaper but better for your company because you can hire a lot better software developers. The only downside is that you can’t directly talk to your developers and clearly talk about what you would like your product to be like. Hiring a good project manager is key to help you get your vision right to convey to the rest of the programmers and make sure they are using their time wisely.

From the blog CS@worcester – CS Blog by Gautam by csblogbyg and used with permission of the author. All other rights reserved by the author.

The Pain of IOS development

I have done some work on IOS apps, and the frustration of apple’s closed system is sometimes baffling. Testing for older IOS version is an extreme pain with Xcode. In order to test for older versions of IOS apps, you either need an older version of Xcode that only works on older version of Mac OS, or you need to have a device with older version of the IOS available. If you don’t have neither of those options, tough luck, either restrict the IOS version your app can run on or pray that no serious bug occurs on the older version of IOS.

Now the certificates and profiles is certainly the most frustrating thing about the app.  Getting an application to run on a physical device may be one of the most confusing part of IOS development. In order to test on physical devices, you need to publish to that device. In order to do that, you need a developer profile with a specific certificate.  That sounds easy right? Wrong, half of the time it’ll throw up an error on your profile, another half of the time your certificate is wrong.  Apple must’ve focused all their time on writing the API, which Android really should read and study, and gave one intern the job to write the profile and certificate documentation. Half of the time you are wasting entire days browsing through Stack trying to fix the issue, which most of the time results in people telling you to do a clean reinstall.

People have always been clamoring for IOS to become more open sourced. Apple certainty have started to lean in that direction, with free developer accounts and the opening up of various IOS functions such as Siri. Unfortunately, Apple probably will never ever budge on certificates and profiles, it is their draconian way to enforce control on the apps that is allowed on IOS. Unless some major upheaval happens to Apple in the near future, we can only pray they streamline the profile and certificates.

Troubles for developing for IOS

https://medium.com/@Pier/why-i-hate-ios-as-a-developer-459c182e8a72#.o1suku996

 

Further Readings this week:

A Paper that shows that TDD has no real improvement compare to TLD

http://dl.acm.org/citation.cfm?doid=2961111.2962592

GItless: an experimental version control

http://gitless.com/

Learning JS in 2016:

https://hackernoon.com/how-it-feels-to-learn-javascript-in-2016-d3a717dd577f#.bmrvue7ju

Software patents may be coming to an end:

http://fortune.com/2016/10/03/software-patents/

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

Protect yourself

This article I read talks about how much different everything in our society is now. Instead of work being done in a work environment, can now easily be done from pretty much anywhere, in a Wendy’s with your laptop, or even literally anywhere, right on your phone. With this thought in mind, just as we pass technological barriers and discover new boundaries, we are also growing more and more vulnerable to having our systems breached by others. With all our privately stored and personal information being available to whoever can grab it has made us a very vulnerable creature. Sometimes we need to take precautions to try to help ourselves from cyber crime. Some of the ways we could do that were also mentioned in this article. They talk about many software based solutions that they think all business leaders and entrepreneurs should be using today. Because using wifi at cafes and coffee shops can be a security risk, people should not be making payments using their phone at a random coffee shop, especially without a VPN or Virtual Card Numbers. That way, even if they have stolen your information, they can’t make any further purchases.

From the blog CS@worcester – CS Blog by Gautam by csblogbyg and used with permission of the author. All other rights reserved by the author.

Decision Table-Based Testing: the setbacks & the benefits

Decision tables are one of the more powerful functional testing methods, partly due to their logical decision-making structure. Here is how they work:

  • Conditions are identified as inputs; actions are identified as outputs.
  • In certain cases, the conditions are equivalence classes.
  • For every possible combination of inputs, the output is identified and marked.

The size of a decision table is greatly impacted by the choice of conditions. Thus, the conditions have to be identified wisely.

Pretty straight-forward thus far. Decision tables involving equivalence classes have a characteristic appearance.

But people often make mistakes when the conditions refer to equivalence classes. Particularly when the equivalence classes are mutually exclusive, and are disjoint sets. As such, it is not possible to have a rule where two entries are true. For a particular rule if one equivalence class is marked true, it doesn’t matter what the other classes are marked – don’t care entries. Thus, the number of rule count increases.

This creates a problem.

Let’s say we have a decision table as shown below, where c1, c2, c3 refer to conditions and a1, a2, a3 refer to the actions. And we have Rule 1-4 identical to that of rule 9. Let’s say we have two versions of this table. Although version 1 is redundant, it does not have a problem. In the second table there is a problem. Because, in addition to being redundant, the two redundant rules (1-4) and 9 are not identical – their action portion differs.

   Frist Version.                                                   Second Version

12

This problem of redundancy and inconsistency creates tremendous strain on the part of a developer. In cases such as that of version two, two observations can be made:

  1. Rules 1-4 are inconsistent with that of rule 9.
  2. The decision table is nondeterministic.

Here is the bottom line: Care Should Be Taken When Do-Not-Care-Entries Are Used in A Decision Table.

This is the drawback of decision-table based testing, because of the dependencies in input domain. On the other hand, the benefits of decision-based testing are that indiscriminate selection of input values from equivalence classes as done in other testing methods such as boundary-value testing (this is done when the variables are assumed to be independent) are not made here. In a decision table, impossible rules are emphasized with the use of don’t-care-entries and the use of impossible-actions.

In summation, decision-table based testing should be used for applications that indicate these characteristics:

  1. Prominent if-then-else logic.
  2. Logical relationship among input variables.
  3. Calculations involving subsets of the input variables.
  4. Cause-and-effect relationships between inputs and outputs.

 

Works Cited

Jorgensen, Paul C. “Decision Table Based Testing.” Software Testing: A Craftsmen’s Approach, 4Th Edition. New York: Auerbach Publications, 2013. Safari Books Online. Web. 7 Mar. 2016.

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

On learning

As I made my way through some blogs this week, one in particular really stuck with me. It is a testing blog, but the post the blogger made wasn’t really necessarily about testing, well not any method of testing anyhow. It was about learning. What struck me about it is this. I sometimes wonder how I am going to actually make sense of everything I am doing in school and how I am going to put good use to the skills when I graduate and how can I better my skill set in ways beyond coding, testing etc. The blogger starts out by saying that she likes to learn and she thinks of testing as an exploratory process and that testing is a learning activity. She has some really good ideas that I may try in the near future. She speaks at conferences and such and learns from the people she meets there and recommends going out and volunteering to help set up and organize a meet up or volunteer to speak and such. I have been to meet ups and try to go as often as I can with my schedule, but have never thought about volunteering to set one up or given much thought that it is actually a learning experience in itself. I have started to do more I this area at school with trying to get the ACM chapter going with the help of some peers and faculty and I can’t wait until it happens. I see good things from it and it can only benefit people. I am always looking for new ways to learn something or new ideas on programming and I wonder what other people do to help become better at what they do or to better themselves. Ultimately I would like to get into a mind set that the blogger has about testing and think of it as a learning activity. That and other things and challenge myself to find new ways to learn.
Here are the links of my weekly reads:
http://visible-quality.blogspot.com/2016/10/sharing-is-way-of-learning.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+mottestingfeeds+%28Testing+Feeds+-+Bloggers%29
http://james-willett.com/2016/10/finding-the-balance-between-unit-functional-tests/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+mottestingfeeds+%28Testing+Feeds+-+Bloggers%29
https://www.stickyminds.com/print/article/testing-unexpected-shift-right-devops-testing
http://feedproxy.google.com/~r/mottestingfeeds/~3/R8IdhiiCjUI/
http://testavimas.blogspot.com/2016/10/how-can-i-break-it.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+mottestingfeeds+%28Testing+Feeds+-+Bloggers%29

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Being Groovy

This week I came across an article called Why Test Engineers Should Learn Groovy (http://testerstories.com/2013/08/why-test-engineers-should-learn-groovy/).

Groovy is a lightweight, object-oriented language that runs on the JVM and it follows Java semantics. It is particularly useful for writing test scripts. The one thing that I really liked was how little typing I needed to get something done in Groovy compared to Java.

Take the following Java code for example:

public class Greetings {

public static void main(String[] args) {

for(int i = 0; i < 10; i++) {

System.out.println(i + “,”);

}

System.out.println(“Testing Groovy”);

}

If the code above is saved in a file with extension .groovy, you could run it by saying groovy fileName.groovy  (you do have to install groovy first). You could compress the Java code above into:

for(int i = 0; i < 10; i++) {

System.out.println(i + “,”)

}

System.out.println(“Testing Groovy”);

This code does the exact same thing as the first code, but with a lot less lines. Groovy does not require you to have all logic within a class. And notice, Groovy does not require semicolons after statements. This code can be compressed even further:

for(i in 0..9)  { print(i + “,”) }

println(“Testing Groovy”)

Groovy makes life a lot easier, everything does not need to be enclosed within a class or enclosed within a main method within a class.

 

From the blog Software Testing – The blog about software by Sudarshan and used with permission of the author. All other rights reserved by the author.