What is recovery/error testing? 

ilk Test is a Functional testing tool product of Seague software. It uses the language called 4GL(fourth Generation Language).

It has 2 components,
Silk Test Agent - Run on remote machine
Silk Test Host - Creating, Modifying, Viewing the scripts

Uses of Silk Test tool:

1. It’s a tool developed for performing the regression and functionality testing of the application.
2. It benefits when we are testing Window based, Java, the web, and the traditional client/server applications.
3. Silk Test help in preparing the test plan and managing them to provide the direct accessing of the database and validation of the field.

Requirements tracing, a process of documenting the links between the requirements and the work products developed to implement and verify those requirements. Requirement Traceability Matrix (RTM) is a document which records the mapping between the high-level requirements and the test cases in the form of a table. The RTM captures all requirements and their traceability in a single document delivered at the conclusion of the life cycle. 

That’s how it ensures that the Test Plan covers all the requirements and links to their latest version.

TDD is an acronym for Test-Driven Development. TDD is a software development process that relies on the repetition of a very short development cycle: first the developer writes an (initially failing) automated test case that defines a desired improvement or new function, then produces the minimum amount of code to pass that test.

TDD is an iterative software development process where you first write the test with the idea that it must fail.

This is a different approach to the traditional development where you write the application functionality first andthen write test cases. The major benefit of this approach is that the code becomes thoroughly unit tested (you canuse JUnit or other unit testing frameworks).

Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification.

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