Go through it, and think about things like the seven testing principles.
If I were to interview you, I'd also throw a whiteboard-ish test at you: I'd pose a problem to you (say, I'd explain a function) and ask you to find test cases.
It's been my observation that this kind of exercise is pretty good at separating the wheat from the chaff: I could see who dares to ask questions, I could see who systematically walks the problem space, I could see who even thinks of testing not just the functional requirements, but also the non-functional ones. Most importantly, I could use this as a way into a discussion, and see how people carry themselves in such a (vaguely work-like) situation.
I suspect the interviews I conducted were on the more rigorous side, so you might be spared whiteboard tests, but in any case it can't hurt to to try and exercise actually creating and reasoning about test cases.
Also, it can't hurt to find out about the testing tools they use. Either you can find them outright, or you can at least make educated guesses about what they use based on the technologies they build their product on. Actually trying them out would be asking too much, but at least get a feel for what their purposes and limitations are.