1) List down usecases (taken from business cases) from function specs. For each use case write a test case and categorize them into sanity tests, functionality, GUI, performance etc. Then for each test case, write its workflow. 

2) For a GUI application - make a list of all GUI controls. For each control start writing test cases for testing of the control UI, functionality (impact on the whole application), negative testing (for incorrect inputs), performance etc.  

In GUI testing, need to cover the customer requirement if don't have to validate  Font size, colors, spellings(labels) etc.

Every application should follow Microsoft rules like

- Controls should be Initcap (i.e every label should start with Capital letter )Can observe that in Win applications every label starts with Caps

- OK or Cancel button should exist

- Controls should not be overlapped

- Controls should be alligned properly (left side alignment is mandatory but the right side is optional)

- Controls should be visible

- Short cut keys should be provided

- System menu should exist (i.e if u press Alt key + Space bar a menu will appear at the left most corner )

- Mouse pointer events 

Colors, Label Names, Tab Order, Alignment, graphs , Navigation of the software to test in GUI Testing.

1) List down usecases (taken from business cases) from function specs. For each use case write a test case and categorize them into sanity tests, functionality, GUI, performance etc. Then for each test case, write its workflow. 

2) For a GUI application - make a list of all GUI controls. For each control start writing test cases for testing of the control UI, functionality (impact on the whole application), negative testing (for incorrect inputs), performance etc. 

Generally,test plan document is prepared by TL&QM.

Entry &Exit criteria is part of test plan document

Entry criteria is 

- Testing environment established

- Test cases prepared

- Build received from development team

Exit criteria is

- All modules are covered or not

- All test cases are completely executed or not

- All bugs resolved or not

“In software testing, a test harness or automated test framework is a collection of software and test data configured to test a program unit by running it under varying conditions and monitor its behavior and outputs. It has two main parts: the test execution engine and the test script repository.”

Recovery/error testing is testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

Security/penetration testing is testing how well the system is protected against unauthorized internal or external access, or willful damage. This type of testing usually requires sophisticated testing techniques.

Parallel/audit testing is testing where the user reconciles the output of the new system to the output of the current system to verify the new system performs the operations correctly. Let us say, for example, the currently software is in the mainframe system which calculates the interest rate. The company wants to change this mainframe system to web-based application. While testing the new web based application, we need to verify that the web-based application calculates the same interest rate. This is parallel testing.