Category Archives: Software Testing

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.

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.

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.

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.

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.