Hi all,
Finally! I have some time to post something new here. As time goes by, the challenges I face gets tougher by the day. Remember some time ago I talked about memory leaks that occurs due to design flaws and abuse despite having a good high-level memory management pointer container?
Well, my talk has just caught up with me once more. It seems that the simple case of allocator race leak is no longer that simple. Usually, we’re always on the illusion that the memory we allocate is the same memory that is supposedly deallocated immediately (alike the allocator when sourcing out for RAM).
But no. This is indeed not the case.
Read on to find out why…
Read the rest of this entry »
Dear all,
I’ve gone into a retreat within the deepest recessions of creativity. Thus I will not be able to make posts for the next few months unfortunately.
However, during this period, I’ll try to eek out some time for a post if I can help it.
Something’s big is coming up.
All shall be revealed by the end of June 2011.
Regards,
Jeremy
This week, we’re going to talk about OoI and OoD.
Don’t get me wrong, they’re not meant to be read literally.
OoI stands for Order of Initialization
OoD stands for Order of Destruction
The former applies to all programming language with object (or memory buffer) constructs while the latter only apply to C/C++ only. Or does it?
So what’s so problematic about them that leads to software quality issues?
Read on… Read the rest of this entry »
Dear all,
It has been quite some time since I’ve posted. And I must say, I’ve been thinking through about the next set of software quality parts and I do not feel very comfortable posting them here. The primary reason is due to the fact that those articles are highly subjective and debatable. It’s unlike the first 12 parts where all of the components described are actually in practice.
Thus for the next few weeks, since my 2nd set of software quality isn’t ready for release, I’ll try my best to share my other experiences too.
This week, we’ll talk about a small change that can lead to a very irritating development cycle. So what’s that?
Read on… Read the rest of this entry »
Hi all,
This week’s post comes a little later than usual because I’m not satisfied with the quality of my draft. After some serious thoughts and revamps, I’ve managed to rewrite the article to better serve this week’s topic - Dangers of using stubs.
By the end of this post, we’d have covered most, if not all of the basics in Software Quality.
We’ll then move on (continuing on the series) to other parts of software quality processes which can help you in your daily development or higher level processes.
So what’s so dangerous about stubs? Let’s find out…
Read the rest of this entry »
Dear all,
There has been some weird issues going on now that I can’t upload Software Quality part 12.
Please hang on while I try to resolve the issues here. Will share this article asap. Sorry for the delay.
Regards,
Jeremy
Hi all,
This week we’ll talk about stubs in greater detail. We’ve seen how stubs can be a useful helper and there’re many types of stubs as well.
We’ll also need to cover some hidden dangers of stubs and mock objects as well.
So what’s so dangerous about stubs and mock objects anyway? Let’s find out. Read the rest of this entry »
Dear all,
Time to move on to the next topic in Software Quality! Today, we’ll talk about stubs and clear up the myth between stubs and mock objects.
Stubs are commonly used a temporary gateway to tackle missing implementations. The question is how is this gateway being implemented. Many a times, people might as well just do an entire class to mock the entire functionality. Well… so is that a mock object or stub?
What are their differences?
Read on more to find out… Read the rest of this entry »
Dear all,
As promised, today we should be able to wrap up coverage completely and call it a day. Coverage has been a big topic as we all know and has so far taken up quite a few posts for the last few weeks.
Today we’re going to discuss the last coverage metric - Modified Condition Decision Coverage (MC/DC).
What’s so important about this coverage? Who should pay extra attention?
Let’s find out! Read the rest of this entry »
Hi all,
This week, I’ll continue to describe the last 2 types of coverage which falls under condition-based category. Just a recap, last week we’ve covered line-based and snippet-based categories of coverage.
Why didn’t I finish off the post by covering the last 2 coverage types? First of all, they’re significantly more important than the rest of the coverage types. Secondly, it’s not as straightforward as any of the coverage types.
To be specific, today I’ll just cover Simple Condition Coverage only due to the amount of explanations and materials required for the details. I’ll cover MC/DC next week. So, please bear with me till then.
So why are they so special? Read on…. Read the rest of this entry »