no brackets for one-liners.

we use camel case naming convention except of the C-code in NSL. So, colName, etc.

no need for an extra assignment. The string is initialized as an empty string.

no i18n here and below in other printError calls?

where are the deletes for these arrays?

put h3 tags outside of the i18n call here and in other similar places in the code.

i18n?

i18n?

where are the deletes for these arrays?

one tab too much here?

all m_* are private and should be part of the private section.

why not to use Qt::GlobalColors instead of QString for the color?

wrong indentation here.

no brackets for one-liners

define variables just before you need them

why qSqrt and not sqrt from cmath?

define variables just before use

too many parantheses

too many parantheses

How to decide which to use ? qSqrt or sqrt?

printError function calls printLine function which inturn calls getLine function and getLine function converts message to i18n string

This is implementation of getLine function:

QString HypothesisTestPrivate::getLine(const QString& msg, const QString& color) {
	return i18n("<p style=color:%1;>%2</p>", color, msg);
}

Now, I have added deletes for every memory allocation with new keyword

does i18n will try to translate these tags along with other content or will it recognize these tags?

It is there in function implementation of getHtmlTable

getHtmlTable make use of i18n.

will m_* will be done for private functions or only for variables?

I would suggest to always choose the function with the minimum requirements. So C/C++ before GSL before Qt. This may not be always consistent right now, but most of time it ensures less conflicts and best portability.

I am using this color variable in Html

	 "<p style=color:" + color + ";>" + i18n("%1", msg) + "</p>"

Hence, I thing QString would be best choice