I've had several tasks where I'm to do functional testing (and to be writing automated test scripts) on features that are not actually complete.
For example, CRUD testing on a project to make sure the user can create, read, update, and delete items. As I begin the create process, I type in all of the fields and hit a button that says 'Next'. On the mock-up and wireframe, there is a specific page that is supposed to follow as a result of clicking the 'Next' button. Expecting this page to appear, the page I used for creating said item is instead refreshed- but the item does get added to the list as expected (though it's data is incomplete because there is supposed to be more information to add after clicking 'Next').
I've had several tasks like this, where I'm functionally testing and attempting to write automated scripts for features on projects that aren't complete. To me, unit testing (testing the code itself) during this stage of development makes sense; functional testing does not. I am new to SQA and a fresh professional in the software world so I don't know if my inexperience is getting in the way. I then get confused because I'm being told to test a feature that I expect to be "done" but, by referencing documentation, really isn't complete. I then scratch my head thinking I've got something wrong, which is shortly followed by me interrupting a developer to ask him/her if I am missing something; this seems to be an inefficient use of time.
Is this the proper way to do testing? Should the features of a project be complete first?