Best way to write unit test in C++ for code

Question

2.00/5 (2 votes)

See more:

Hello, if a program was not written in a way with proper functions with the given input, what would be the way to write an unit test or integration test, that is the output that is to be compared at the end in a unit test is not contained in a function, should I change the code to contain everything in a function for a particular output that im supposed to get?

What I have tried:

I have tried writing it but have no idea what to call as the value that Im supposed to test is not contained in a particular function taking particular inputs

Posted 1-Oct-20 10:42am

Member 14589606

Updated 1-Oct-20 23:24pm

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CPallini · Answer 1 · 2020-10-01T20:06:00

Solution 1

The proper way is to treat it as a black box, providing appropriate inputs and checking if expected outputs are produced.

Posted 1-Oct-20 20:06pm

CPallini

KarstenK · Answer 2 · 2020-10-01T23:25:00

Testing is an art of its own, but the best way it to test the real release functions and NOT change them, but for testing it is often needed to write a bit more explicit.

When testing functions it makes sense to test all possible input, so include also invalid and error prone values. Like for an integer negative values and null and MAX_INT.
For string input also the empty string, null string and long values are needed.

Read about "Test Driven Development" for further insight like test coverage and integration tests.