Blackboard assessments are a good way to monitor student progress in your course. In the Grade Center, you can access valuable statistics on test responses, as well as overall grade distribution. Additionally, for certain types of questions (multiple choice, T/F, fill in the blank, etc.) Blackboard will automatically grade for you.
Surveys work exactly like tests, except the Grade Center will display complete/incomplete status rather than a grade. Also, surveys are anonymous. There is no way to discover individual responses to survey questions.
There are many combinations of options that can be configured when deploying tests. For that reason, we recommend that you work closely with your Blackboard Support Team the first time you deploy a test, or that you deploy a practice test to ensure that both instructor and students understand the testing and results process.
Documentation on tests and surveys:
Tests, Surveys and Pools
1) Test availability exceptions - When you set up your test options (availability window, number of attempts, time limit), sometimes you have a student or group of students who need to have a different set of parameters. Prior to SP13, this has required creating a copy of the test in order to set the options differently for these students. Now, you can set up parameters to define a set of students and apply different options to them within the original test's options:
2) Feedback release options - improved granularity of choices - which types of feedback will be released based on which set of conditions:
*If you elect to release scores or feedback based on all attempts being graded, you will need to enter a grade for EVERY STUDENT. Thus, any student who does not submit the test, and is currently showing a null grade (-) in the Grade Center, will prevent the grades being released until you enter 0 instead of null for those records.
**BUG ALERT: On tests that are automatically graded within Blackboard, even if you set up these options to NOT release the grade, the grade will be released. Blackboard is aware of this bug and a patch is being developed.
3) Test access log - This feature will let you see who has accessed the test, and during what time period: