Ok so I have been a QA for quite some time but have never had to write up a test strategy for SharePoint app. To be exact MOSS 2007. Does anyone have any good resources that I could access to learn how to go about creating a test plan/test strategy for SharePoint project?
THAT is what I am trying to find out. Since I have never tested SharePoint before I do not know the answer to that question I am asking that question. If there is no difference great. But I would rather ask a question that be sorry later on.
What are your sharepoint requirements?
What must it do for the users?
What must work?
What must it NOT do?
How must it perform?
What standards must it meet if applicable?
What security measures are in place and do they work as intended?
Ah but see these types of questions would be asked of any type of software you would test. maybe for SharePoint heaview on Security and Performance side but that is about it.
My question is are the any special consideration for SharePoint specifically. I didn't think so but needed to make sure since my employer is looking to me to create slides that specifically outline the SharePoint - MOSS test strategy.
On top of the usual approach stuff as JakeBrake said above.
We do some testing on MOSS 2007 and I take the following view.
- Out of the box functionality is not tested by the test team. Part of installation is to run through MOSS to check that it is installed correctly
- Custom configuration should be tested by the test team. Generally the estimate for this is much less then it would be for testing actually new code/product, otherwise the testing does not really vary from any other site (although the browsers are limited generally to IE)
- Customer web parts should be tested by the test team as a normal project.
I think that covers it from a high level point of view (obviously stick in your normal strategy, whatever you place normally does)