Inform the team of your status, and use available time for professional development. What you can say at the standup, in such circumstances, is 'Still waiting for x: in the meantime studied up in HTML5/CSS3/Canvas-Object as implemented in Chrome'. If some of your coder pals get upset at your training window, they might dump some work on you to keep you busy.
I've heard stories of government contracts where people were supposed to design, code, test, and document the system in parallel. Needless to say, much effort is wasted and the project doesn't get done any sooner or any cheaper.
Often the people 'blocked' are in Unit Testing, Integration Testing, Technical Writing, or similar roles that only become active toward the end of the development cycle.
In such circumstances one can use the opportunity for professional development, whatever that means in your discipline. For technical writing one suspects this is focused on online-help development tools, screen capture and cropping tools, 'infographics', etc. If you're a coder in some capacity then it may not matter whether you're focus is on QA - probably any coding area is worthwhile.