+1 Yasir.
On Wed, Aug 17, 2011 at 11:39 PM, Yasir wrote:
> For questions specifically asking about test cases, I would suggest
> following 3 step approach:
>
> First think of a* basic flow that MUST work for the application* (what is
> expected with the application. Firstly make it clear with you interviewer).
> eg:
> 1) User should be able to open Notepad without any error/warning.
> 2) User should be seamlessly able to type characters. (should not be
> the case, where you are typing and it appears after some time)
> 3) Create one file using notepad, close the application and reopen the
> file. (make sure, result is as expected)
> ..and so on (try to cover all basic functionality). Also you can
> club few test cases. eg, for menu features you can say something like:
> verify that all menu options are working as expected.
>
>
> Now move one step ahead, and *think of a person who is not familiar with
> the application* (what would he do?):
> eg:
>1) User should be able open the Help docs and help docs should be
> relevant.
>2) If a user writes something, forgets to save and trying to close
> the application: Appropriate notification.
>3) Trying to copy and paste with supported/unsupported format.
>4) Drag/drop a file on the application.
> and so on...
>
> and then comes *negative test cases* (it may happen rarely but it is very
> important):
> eg:
> 1) Trying to open multiple instances of the application
> (application shouldn't act weird)
> 2) Crash the application and open it next time. It should open (may
> be with some notification), but the application SHOULDN'T CORRUPT.
> 3) Application behavior when you open very large file. (should give
> appropriate warning, if it is going to take longer time/crash)
> 4) behavior with unsupported file. (eg: trying to open a .out file)
> ..and so on...
>
> In my opinion, with this approach you will be able to write good test
> cases. Just think on the line above mentioned 3 steps.
> You may come with different test cases, but your test cases will also
> ensure that application is working fine in most of the cases. :)
>
>
> Any suggestions on above approach?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Algorithm Geeks" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/algogeeks/-/POcIPzZSlbYJ.
>
> To post to this group, send email to algogeeks@googlegroups.com.
> To unsubscribe from this group, send email to
> algogeeks+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/algogeeks?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Algorithm Geeks" group.
To post to this group, send email to algogeeks@googlegroups.com.
To unsubscribe from this group, send email to
algogeeks+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/algogeeks?hl=en.
