User forums > General (but related to Code::Blocks)

Is there any plug-in for auto-testing?

<< < (2/3) > >>

benjamin_t:

--- Quote from: beqroson on November 15, 2013, 03:09:00 pm ---
--- Quote from: benjamin_t on November 14, 2013, 02:03:12 pm ---I am hoping to find an auto-test plug-in like the JUnit plug-in for eclipse. Is there anything like that or not? If not, I really hope somebody can develop one, that would be very helpful. ;)

--- End quote ---

Hi, I am looking for suggestions of plugins that need to be developed. Oh, there is one. Ok, then, I could perhaps develop this, so called auto-test plugin for CodeBlocks. Would that be very helpful?

--- End quote ---

Yes, that would be very helpful, maybe you can try to incorporate cppUnit.

oBFusCATed:

--- Quote from: benjamin_t on November 16, 2013, 06:40:16 am ---Yes, that would be very helpful, maybe you can try to incorporate cppUnit.

--- End quote ---
Or UnitTest++, Boost.Test, Google.Test, testframework.xxx, etc...

beqroson:

--- Quote from: oBFusCATed on November 16, 2013, 12:20:20 pm ---
--- Quote from: benjamin_t on November 16, 2013, 06:40:16 am ---Yes, that would be very helpful, maybe you can try to incorporate cppUnit.

--- End quote ---
Or UnitTest++, Boost.Test, Google.Test, testframework.xxx, etc...

--- End quote ---

Wouldnt this make the CodeBlocks IDE too good? I mean, a plugin that manages test framworks similar to how it manages compilers. That would make CodeBlocks one step further to become THE development app; free, open source, broad compatibility, multi platform. I mean, that would not be desirable, now would it.

oBFusCATed:
In fact using UnitTest++ works already, there is one small feature missing, but it is not such a pain.
I'm sure other frameworks will work, too.

I've never used JUnit, so I don't know what are the requirements and benjamin_t never stated them explicitly.
But I guess he wants to have automatic test generation, setup, etc...

beqroson: I'm not sure what is your goal, but it is better to concentrate on something you don't like in C::B and try to fix it.
                 Or if you want to fix just something in C::B go to our bug tracker at berlios and choose a random bug and fix it, then post a patch.

beqroson:

--- Quote from: oBFusCATed on November 16, 2013, 01:45:51 pm ---beqroson: I'm not sure what is your goal, but it is better to concentrate on something you don't like in C::B and try to fix it.
                 Or if you want to fix just something in C::B go to our bug tracker at berlios and choose a random bug and fix it, then post a patch.

--- End quote ---

I am just extremely analytical, oBFusCATed, not biased. The thing that I find to be of concern is that none of the developers is getting paid for this. I am not saying they should be paid, nor that they should not be paid.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version