Question pattern of Microsoft's manual testing paper

It will compromise of four section.
1. Analytical ability
2. Testing
3. RDBMS
4.C,C++/.NET/JAVA  (One is manadatory)

1.Analytical ability: It will contain aptitude question like figures, cartesian product, Rank, average.
Q If ghjikl is written as "hijknld" then oiundf can be written as
Q If a likes b
    and b likes d  then like a likes d type question.

2. Testing: Prepare for the ISTQB type questions.
3. RDBMS: Basic questions of select query , delete query, normalization, denormalization,  keys, views etc.
4. C++: General questions of output, complile and run time error and abstract class etc.

And best of luck , if you are going to appear.
Himanshu Jain
9899180227
http://www.facebook.com/jainhimanshu1986

what it test incident report?

Test Incident Report: detailing for any test that failed the actual versus expected result and other information intended to throw light on why a test has failed. This document is deliberately named as an incident report and not a fault report. The reason is that a discrepancy between expected and actual results can occur for a number of reasons other than a fault in the system. These include the expected results being wrong the test being run wrongly or inconsistency in the requirements meaning that more than one interpretation could be made. The report consists of all details of the incident such as actual and expected results when it failed and any supporting evidence that will help in its resolution. The report will also include if possible an assessment of the impact upon testing of an incident.


Format:

Date: ___________

Project: ____________

Programmer: __________________

Tester: _________________

Program/Module: _______________________

Build/Revision/Release: _______________

Software Environment: _________________

Hardware Environment: _________________

Number of Occurrences: _______

Severity: _________

Priority __________

Detailed Description: ___________________________________________________

___________________________________________________

___________________________________________________

___________________________________________________

___________________________________________________

Assigned To: ___________________

Incident Resolution: ____________________________________________________

Himanshu jain 

What is Functional point analysis(FPA)?

FPA is a method to determine the functional size of an information system or project. The functional size may be used for different purposes, for example budgeting. The measurement is independent of the technology. This measurement may be used as a basis for the measurement of productivity, the estimation of the needed resources, and project control.
 
FPA carries out the following steps to determine the size of an information system or system development project:
• Step 1: Identify the functions of the system that are relevant to the user
• Step 2: Determine the functional complexity of each function
• Step 3: Calculate the unadjusted function point count of the system
• Step 4: Rate the general requirements for the system using the 14 general system characteristics
• Step 5: Calculate the adjusted function point count of the system