RE: The following questions answers pls posted to the ...
1.Non-functional testing involves Basic GUI testing System Integration testing volume testing and all other tests wherein we not going to verify and validate the functionality of an application like for example:
A basic Windows login test would involve just testing the quality of interface and proper placing of controls but we wont be verifying whther its properly authenticating users.
RE: The following questions answers pls posted to the ...
Hi
Usablity stress load compatible etc are related to nonfunctional testing whereas testing related to the business requirement is functional testing.
for example: functional testing in yahoo mail server is creating the new yahoo user whereas nonfunctional is testing the server response time user concurrencies and so on.
RE: The following questions answers pls posted to the ...
1) Non-Functional testing means where we are testing the non-functional features of the application. even performance testing usability testing gui tesing comes under Non-Functional testing where as they have some importance role on application..
2) System testing means we have to take whole system as a single unit and test it. may be inside that system there are so many modules but in S.T we are not bother about the individula modules. give the input and check the final out put of the system as per requirement.
3) System Integration Testing means we have to check the interface between the different systems or may be in between the different modules on a single system.
RE: The following questions answers pls posted to the ...
1)as name says what all doesn't come under functional are called as non-functional. we have 6 types under dis i)configuaration testing ii)compatability testing iii)recovery testing iv)intersystem or end-to-end testing v)internationalization or multilinguity testing vi)installation testing
RE: The following questions answers pls posted to the ...
Since we have quiet a few answers for the first question i will leave it alone
(2)System Testing: Testing an application to ensure that it meets its functional and non functional requirements. Functional Techniques: +ve _ve Random Smoke ect Non Functional: Stess Load Volume Reliability etc
(3)System integration Testing: The objective of System Integration Testing is to provide confidence that the application under test(AUT) is able to interoperate successfully with the other software systems in the live environment.
as far as techniques concerned you could use Compatibility and Reliability.