Archive for the 'JPicus' Category
Ping pong
How do you “ping pong” in software development?
1. You have a bug.
2. The bug is hardly reproducible, but when reproduced it appears to be very serious.
3. There are a number of teams involved in the functionality where the bug is found.
As a result what actually happens in most of the cases is “ping pong”. This [...]
[ Back to top ]
Unit testing a wizard
I will again use JPicus and its only wizard (for now) to share my experience with testing wizards.
Wizads have always been a subject of low code coverage and no unit testing. Many examples could be given were the whole test suite of a project is green, but when a user starts using the product there [...]
[ Back to top ]
The “entry point” to JPicus. A well tested view.
From an end user point of view the “entry point” to JPicus is the AgentConnectionsView.
Similar to every view in JPicus, the AgentConnections view is 100% covered with unit tests. This view specifically has 95.9% (71 lines) covered with unit test and 12.1 % (9 lines) covered with an integration test.
First - the provided functionality:
The AgentConnections [...]
[ Back to top ]
JPicus - the tool for Java I/O analysis
“If I want to read something nice, I sit and write it myself!”
Mark Twain
I heard this quote just a few weeks ago. Do not know whether it is really Mark Twain that said it, but it is an interesting quote.
This is one of the “jokes” a friend of mine used in his presentation at JavaOne [...]
[ Back to top ]
