Reminder: Initial Discussion Board posts due by Friday, responses due by Tuesday
Students will be expected to post their first initial discussion board posting by Friday of each week. Discussion posts will be graded and late submissions will be assigned a late penalty in accordance with the late penalty policy found in the syllabus. NOTE: All submission posting times are based on midnight Central Time.
Students are expected to post their responses to peers by Tuesday. NOTE: All submission posting times are based on midnight Central Time.
Primary Task Response: Within the Discussion Board area, write 400–600 words that respond to the following questions with your thoughts, ideas, and comments. This will be the foundation for future discussions by your classmates. Be substantive and clear, and use examples to reinforce your ideas:
Your customer on the current software development project would like to know how your team will identify the required test cases for your product as you enter the test planning phase of the project. Describe the purpose of white-box testing, the techniques available for white-box testing, and some examples of how your team will use white-box testing to view the structure and flow of the software. Finally, contrast the test methodologies between black-box and white-box testing.
Ensure that you respond to at least 2 other students providing their view of the white-box and black-box testing process, and ensure APA format is used
Responses to Other Students: Respond to at least 2 of your fellow classmates with at least a 100-word reply about their Primary Task Response regarding items you found to be compelling and enlightening. To help you with your discussion, please consider the following questions:
- What did you learn from your classmate’s posting?
- What additional questions do you have after reading the posting?
- What clarification do you need regarding the posting?
- What differences or similarities do you see between your posting and other classmates’ postings?
I will be using White-box testing to identify the required test cases for the software application currently being developed. White-box testing (also known as clear box testing, glass box testing, transparent box testing and structural testing) tests the internal structures or workings of an application, unlike Black-box testing which test the functionality.
I will use a two-step approach when performing the white-box testing. The first step a tester will do is learn and understand the source code of the software applications being developed. The tester should be very knowledgeable in the programming languages used to develop the software application. The second step would be to create test cases and execute those test cases. I will also perform Code Coverage Analysis, which identifies areas of a program that are not exercised by a set of test cases. Once gaps are identified, I will create test cases to verify untested parts of code, thereby increasing the quality of my software product.
Statement coverage technique requires every possible statement in the code to be tested at least once during the testing process. Branch coverage technique checks every possible path (If Else and other condition loops) of the software application. I will also use condition coverage, multiple condition coverage, path coverage and function coverage techniques. All techniques have their own merits and attempts to test all parts of the software code. Using statement and branch coverage you generally attain 89-90% of code coverage. The complexity involved with the white box testing will be determined on the complexity of the application development. The more complex the program the longer the testing may take.
Bing.com (March 29th, 2021) White-box Testing retrieved from https://www.bing.com/search?q=white%20box%20testing&pc=cosp&ptag=G6C19N3878ADEA771B5E1&form=CONBDF&conlogo=CT3210127
Guru99.com (March 23rd, 2021) What is White Box Testing? Techniques, Example & Types retrieved from https://www.guru99.com/white-box-testing.html
Describe the purpose of white-box testing, the techniques available for white-box testing, and some examples of how your team will use white-box testing to view the structure and flow of the software.
White Box Testing
A software testing technique in which we test the internal workings of the software to verify the way that the input-output flows, and to improve the design, the usability and the security of the software being tested. In this type of testing, the code is visible to testers and for this reason it is often called Open box testing, Code-based testing, or Glass box testing. White box testing can help to find structural problems as well as hidden errors and problems with specific components. Because of the code-based element in White Box Testing, programming experience will be needed.
Black Box Testing
A software testing method that covers the functionality of a software without caring anything about the internal structure or design of the software that is being tested and compares input and output values. It is also sometimes called behavioral testing, closed-box testing, specification-based testing. In general, Black Box Testing checks to make sure that the system is working like it is expected to work. Black Box Testing does not require programming experience.
Finally, contrast the test methodologies between black-box and white-box testing.
There are a few contrasts in the two, some are:
Mainly applicable to lower levels of testing like Unit Testing and Integration Testing
Mainly applicable to higher levels of testing like Acceptance Testing and System Testing
The internal structure/ design/ implementation of the item being tested is known to the tester.
The internal structure/ design/ implementation of the item being tested is NOT known to the tester.
Can be done by development team.
Testers need not be highly technical, and it also simulates end user experience.
Can uncover errors early in the development process.
Can often be automated.
Hard to separate the program and the testing environment.
Usually does not capture all software paths.
White box vs. black box: A basic overview of software testing. (2020, October 15). Retrieved April 04, 2021, from https://www.singlemindconsulting.com/blog/white-box-vs-black-box/
What is white Box Testing: Types & techniques for code Coverage: Imperva. (2020, September 24). Retrieved April 04, 2021, from https://www.imperva.com/learn/application-security/white-box-testing/
Vani. (2021, March 27). Black box testing: An in-depth tutorial with examples and techniques. Retrieved April 04, 2021, from https://www.softwaretestinghelp.com/black-box-testing/