Yeah. You sometimes hear rules like "never write tests outside a framework," but this advice is aimed at the junior dev who doesn't want to learn the tooling, not at someone who is necrocoding in a 30 year dead language and needs to decide between loads of copy/paste and rolling their own testing framework (which would get used once, leading to amortization difficulty). Sometimes the constraints really do call for loads of copy/paste, and that's OK.