How do you choose to write your unit tests in C, Sup Forums?

How do you choose to write your unit tests in C, Sup Forums?

You do write unit tests for your C code, right?

Other urls found in this thread:

github.com/Tuplanolla/cheat
twitter.com/NSFWRedditVideo

I don't even write unit tests for my Java code.

What is a unit test?

POO IN THE LOO

>unit tests

>Actually writing unit tests
>Not formally proving your program to be correct

This to be honest family.

Well-designed unit tests could help catch bugs in the implementation of third-party libraries, the OS, and even the hardware.
When you formally prove your program, you do it under the assumption that all those things work absolutely correct.

>bugs in the implementation of third-party libraries, the OS, and even the hardware
Literally not my problem, take it to upstream.

How can I take a bug that I don't even know about yet upstream?

I don't know, ask upstream.

Faggot

I don't.

I wouldn't write code in an unsafe language in the first place.

this guy is on dr. leslie lamport level, aka LLL

unit tests are harder to write than the actual code, fuck that

So you rather tediously test your app manually and thoroughly with every change you make to the code?

Tell upstream to do their job correctly.
Tracking bug in other programs shouldn't be my job

You don't need unit tests as long as you have a public issue tracker.

And you just release your code without testing if it even works because you rely on other people to do the work for you?

Sorry but I am too retarded for writing unit tests.

>tfw not even kidding

how can I unit test avr-code?

I don't

just start with smoke tests and add a new unit test for every issue/bug thats reported and solved.

like every other code, except that you need to add some wires

>like every other code, except that you need to add some wires

Wires? What?

> his code coverage isn't 100%
lolwat, are you an idiot?

I write it in Ada instead

assuming that you want to test routines that get external input on ports or output something (e.g. your uart handler, input from sensors, etc)

>he doesn't even know who pic related is
the door you go

people on Sup Forums are retards who think they are so fucking cool because they can write their useless fizzbuzz and counting-down-from-700-to-200-in-steps-of-13-bullshit in max perofrmant C

they hate actual useful shit like object oriented programming and unit testing

Sometimes.

I test my own input. I don't assume 50 people will all be using the same program on the same machine at the same time.

For games, you can squeeze the performance out of a single place in the draw if more people are going to use it and have all those people play from different places in the machine at the ideal setting be no local collision means at worst you lose individual players.

Yes.

github.com/Tuplanolla/cheat

Looks dead.

There's absolutely no excuse not to write unit tests.

>implying that is even hard to do

OOP "programmers" everyone

>>implying that is even hard to do

that wasn't written anywhere
learn to read, nigger

Way to shift attention away from C and onto what you describe in your authority.

I can't stand python and women.

the way you typed it implied you thought it was hard and it was backed up with liking OOPs

I only use C for microcontroller programming and i only did manual testing so far but you might want to take a look at CUnit

What the fuck are you talking about

i didn't imply anything
you just chose to get offended

>neet lacking reading comprehension

Looks complete.

Abandoned 2 years ago