Category Archives: Software Testing

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.

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.

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.

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.

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.