I got stuck while differentiating Functional and Nonfunctional testing?
Can anyone clear my following doubts -
1) What is Functional Testing with example.
2) What is Nonfunctional testing with example.
3) Difference between these two.
I shall be highly thankful if anyone clear my doubts.
You got your terms mixed up, and if you are not careful you would be advised as follows:
1) Functional testing is performed by someone who is quite aware of what they are looking for;
2) Nonfunctional testing is performed by someone with no idea of what they are looking for;
3) The difference is that you get what you pay for, I suppose.
What you are referring to is requirements. What a set of functional requirements define is exactly what is needed to support the business operation. What non-functional requirements define are all the other types of requirements that relate to an operating environment, standards, interfaces, and those kinds of things that are not unique to the business operation. As a tester you should verify that all requirements are satisfied regardless of their source classification.
The main difference? For many non-functional test scripts you can reuse the same tests (adapted to a specific user interface if necessary) to make sure that the application is properly coded, and for functional requirements you always have to create unique tests.
Did somebody pull your leg and make you study the file of lost memos as well?
All of the above, and then some, but I was trying to stay within the context of what needs to be pooled with what we normally look for in systems testing. It is generally all the stuff that must be accommodated even if the client does not ask for it. That said, you could in fact have defined performance criteria for an application that then form part of the functional requirements. For the majority of projects these non-functional items are imposed by operations. I don't actually like this terminology, but that is another matter.