{{Melissa}} Yes we do. We do it because different people do those tasks, and the tasks overlap, and we need to know when the test scripts are done. That is a date we pay attention to. The two tasks run in parallel to some degree, as well. If they were all in one task, we wouldn’t have visibility into when the test scripts are all complete. If your team were organized such that the person that develops the test script is also the person that runs it, and they do parallel test script development and testing, especially refinement of the test script as they start testing, it wouldn’t make sense to split the work into two tasks, in my opinion. The purpose of adding a task is to manage someone’s expectations, in my opinion. Those expectations need to be crisply defined. Because we’re dealing with separate deliverables from separate people, I’d risk bloating the project to get more clear role clarification and to better set expectations regarding that work. That’s just me, though. Hope this helps! Eric
