Well, after having worked for a considerable number of years in s/w testing, I have a question in mind , which I guess is debatable and would be interesting if more and more ideas flow in and experiences/practices shared.

So the Question is:
Does it matter in any sense for the test team, what platform the development team is working on to develop the application under testing?

I mean, will there be any difference in the testing (test strategy, test plan, test approach, test cases, test automation, test execution, test reporting etc) of the s/w being developed in Java/J2EE platform with that of the s/w being developed in say… .NET

Frankly speaking, I don’t think it matters to the test team in any ways. Whichever platform the development team is working on, the testing activities will be same.

Any disagreements? What say?

__________________
Lack of WILL POWER has caused more failure than
lack of INTELLIGENCE or ABILITY.

-sutnarcha-

Hi Sutnarcha,

If we are going to test the application manually then I will go by your way and there will be nothing to matter for the testing team. The testing carried out will be independent of the platform in which the applicaiton is tested.

But if the testing is carried out using automation tools then there will be slight difference on the approach and it is dependent on the platform in which the applicaiton under test is developed. There will be different add on for different tool in which the application is developed.

It too expect more views on this regard and it is a nice concept posted by you.

REgards,
Ganesan

Hi,

Picking up from Sridhar's exceprts, development plaftorm of the application under test (aut) would definitely not matter to manual testing.
As we are basically involved in functional testing of the application and not interacting with application object properties as such, technology does not play a role.

But where Automation or Performance Testing is concerned, development platform would definitely be taken into consideration as a valid issue while deciding the test approach strategy.
For Automation, selection of tool itself would depend on development platform -

• for instance, QTP / TestPartner would be preferred for applications developed in vb.net, asp.net technologies.
• incase of java applications using swing, we would prefer rational functional tester (java version).

.

This becomes an important criteria in deciding the object recognition capability of the tool.

Same applies for Performance testing. Depending on the application platform, we select the different protocols in which our scripts would be created. We select siebel / web protocols for siebel application, winsock protocol for win32 applications, orcale / ncp protocol for oracle financialsand so on.

Leaving more to the views and opinions of the other geek members, but definitely a nice topic to discuss on.

Nice post sutnarcha!!.

cheers...

__________________
Regards,

V.Umesh Krishnan
QA Consultant

Its really great to be in this thread,
(this kind of debate by expert members )it will be really useful to ppl who are new to software testing!!!

i feel ppl should start from manual testing initially and once they understand the complete life cycle of software testing in manual testing and different testing techniques only then the should move to automation!!!

lets see what other members feel

thanks & regards
trainee_tester

yes it matter,

I think the test cases will change for application developed in java and for the application developed in .net.

The functional test cases will be same, but the functional testing is not the complete testing of any product.

you all have heard about experienced testing, what it is?
It's depend on tech and environment, not just only on test case writing.

__________________
--
Brijesh Jain