A charter summarizes the goal or activity of the session. It is a “clear mission for the session”. You can define a charter before you start your session. It is a statement of how the session will be focused.
The entire session report consists of these sections:
• Session charter (includes a mission statement, and areas to be tested)
• Tester name(s)
• Date and time started
• Data files
• Test notes
Lets see an Example of Session report chart for Login functionality:
Session CHARTER: Login functionality and report on areas of potential risk.
OS | Windows 7
Strategy | Function Testing
Strategy | Functional Analysis
I touched the login fucntionality and focused mostly on valid/invalid login attempt
— Issue on login concurrently with same user