New to the field of QA, I've been asked to do SQA for a project that I'm unfamiliar with and that is close to completion. An example of a specific functional task to be tested looks like the following:

> 
> 51: Rename Excluded Words at the Topic and Subtopic levels to be Not in Topic and Not in SubTopic
> 
> 
> 

I could see how if I was the developer who built the project or had I been roped in on this since the beginning, then it'd be fairly obvious to "Click here" and then "Click this button in the drop down" followed by ... etc, etc. Either because I developed the project or because I've tested the project as it's being built from the ground up (and thus I'd know it inside and out). But because I'm new to this project and it's relatively large, I don't know the steps required to actually get to the part where I "rename excluded words". Hell, maybe it's actually broken and that's why I couldn't find it.

The above is just an actual example, but my goal here is to gain some insight that I can apply to my practice in general. 

**If the SQA is new on a project already in development, should the developer provide steps needed to perform the function to be tested?**

Not necessary *every* step for *every* test (like creating a new user) but strictly for more hidden or complicated features.