Skip to content
This repository has been archived by the owner on Jan 22, 2022. It is now read-only.

Document the requirements on targets #429

Open
davidwagner opened this issue Oct 10, 2021 · 0 comments
Open

Document the requirements on targets #429

davidwagner opened this issue Oct 10, 2021 · 0 comments

Comments

@davidwagner
Copy link

I have heard, but cannot confirm, that no alternative should be a substring of any other, otherwise it will trigger lots of false positives for the cheat detection. For example, # DEFINE VNAME Customer CustomerName is apparently no good. Is this correct?

If this is correct, this should be documented in exam-write/README.md. The restrictions on choosing targets and alternatives needed to ensure the cheat detection works well should be documented there.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant