To put it simply the overall answer depends on what you are looking to gain.
By working in QA you will likely learn the common (and not so common) mistakes that developers make. This will hopefully make you a better developer.
However, the question becomes, what makes your professor think that you would do well in a QA role and not just have a tarnish on your resume?
QA requires a different skill set than development, one that requires you to look at the project as a whole and not just in small sections. While focusing on your functionality in development is acceptable, focusing solely on a singular section in QA would be catastrophic to say the least. Also, it requires the communication and interdepartmental skills that Developers tend to lack in. (I can go on here but I don't feel the need)
Also, who's to say that you, like myself, don't end up just loving QA and realize that you can make just as much of a living in QA while having a less stressful more fun position?