Each test result and correct answer should be a separate record. That allows you to set up a relationship that matches both by test and result to see if the result matches the corresponding correct answer.
And I wouldn't link them by a test name. Say you accidentally mistype that test name and don't spot the error right away. If you later try to correct the misspelled name, you break the link to any records linked by that misspelled name in your relationship and you then have to track them down and correct the error there as well. It's better to link by an ID--either an auto-entered serial number or a text field that auto-enters Get ( UUID ). you can still use the test name to find or select a test, while continuing to link records by an ID.
But if each test has 200 questions, I have 8 test types, and let's just say a minimum of 3 different tests for each test type, I have 24 tests and we are talking entering 4800 different records. Wouldn't it be easier to have response_001 through response_200 in a single record in Test_Results table, and the same in Test_Answers table, and then setup a calculation field for each response in Test_Results table that says that if test_ID = test_ID (between the tables) to compare the response fields? That way, once I set up the 200 calculations in the Test_Results table, no matter the Test_Answer record it is comparing it to, the calculations will be done?
Use separate records.
Whether you enter the data into separate fields or separate records, it's the same size data entry task.
But separate records gives you a flexibility you just can't get if you use multiple fields within the same record.
In case you are doubting the wisdom of Phil and Bruce, let me add my $.02: they're right. Fields will limit your options and actually make everything harder. Sets of Answer records with links to a table of Test records where each Test record is the parent of its own set of Answer records will serve you best.
One thing you might consider is to create your question records from the Answer records. When the test is chosen you have a script that creates a set of records for the test taker that matches certain fields in the set of records that is the Answer set related to the test. Then it will be easier to match them up when grading. You can even include the answer in the question record (and just not show them to the test-taker) to make grading easy and instantaneous.
I also will say that over a decade of experience has taught me that all of these gentlemen are correct. Use records. Big tables should be avoided anyway (wide = lots of fields) FileMaker can handle your record count without breaking a sweat.