Automated Unit Testing

[Justin Prior]

Hi All,

I have been working with TC65/TC65i modules for a long time and the manual testing has become tedious. Recently I have picked a project with the BGS5 and I decided to try get some unit testing going. Unfortunately I have had no luck as of yet, all the J2ME frameworks seem to fail because there is no gui aspect that they all seem to look for.

Has anyone had some mild success in this space?

[Nikita Kapitonov]

Good question! Mee too, want to have a guide for automated testing, never did it before.

пт, 27 нояб. 2015 г. в 1:17, Justin Prior <justinl...@gmail.com>:

Hi All,

I have been working with TC65/TC65i modules for a long time and the manual testing has become tedious. Recently I have picked a project with the BGS5 and I decided to try get some unit testing going. Unfortunately I have had no luck as of yet, all the J2ME frameworks seem to fail because there is no gui aspect that they all seem to look for.

Has anyone had some mild success in this space?

--
javacint group - http://www.javacint.com/
---
You received this message because you are subscribed to the Google Groups "Cinterion Java enabled chips support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to javacint+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Justin Prior]

There really seems to be no options from my goolging around? We are obviously required to mock out certain portions of our code that interface to device specific functions. There just seems to be no bare-bones assert based testing framework that will work with J2ME for embedded applications that aren't mobile phone related.

[Kris Budde]

Hi,

we are doing unit tests for our tc65/bgs5 projects. We are using plain junit for testing.
We decided to not test hardware specific code. Just business logic is tested.

We have a special test build without obfuscation. In a j2se test project we include this jar as dependency. So we can test all classes before installing to modem on the development machine.

Is it this what you are looking for?

BR Kris

[Jérémie Faucher-Goulet]

I agree,

We do develop our applications so they can run on both a pc and all the cinterion chips we support through the use of the microemulator library.

https://code.google.com/p/microemu/

This is done to facilitate development on a pc for business logic while retaining most of the J2ME functionalities working (such as opening a TCP socket and all).

The rest of the hardware-specific stuff we abstract, emulate or mock through interfaces.

For unit testing we simply use the latest version of junit. We setup yet another java project in parallel where we write our tests in the same packages to the code being tested (with a dependency on the first project) so we can use superior versions of Java and all the glory of Java 6, 7 or even 8.

This way we can unit test anything we want in our code, mocking hardware features doing so.

Hope this helps!