test plan and test matrix for our beta version

Criterion for our test:

    If the tested module(s) can work correctly and complete user scenarios, and also it can deal with some unexpected cases appropriately. In addition, the app can response to users effectively and fluently, we will let it pass.

Test Resources:

          Platform: WP7.1 & Visual Studio 2010 & windows phone emulator.

          Testers: Dongliang & Ting Zhang

Test matrix:

	User Type	Mobile    OS	Language	Network
Variable Count	2	1	1	3
	Conf. hosts		English	No network
	Conf. attenders	WP 7.1		GPRS
				WiFi

 

i)        Functional/Performance Test(效能测试): We will test the reliability and stability of each functional module.

          第一部分： we do our test strictly follow our written test cases, and test whether the function is work or not. Following is some examples of our test cases, to see more detail, please refer to our tfs.

         

Test Case	Tested feature	Test Data	Operation	Expected result	Actual result	Test Date	estimated time and tester
1			none	three tile on the favorite page
2			click favorite authors tile	jump to the favorite panorama show all added to favorite   authors
3			click favorite publications   tile	jump to the favorite panorama   publication item and show all added to favorite publications
4		no favorite	click favorite conferences tile	jump to the introduction page   which show how to add conferences to favorite
5		have favorite	click favorite conferences tile	jump to the conferences list   page
6		on the favorite panorama	click an author	jump to the author detail page
7		on the author detail page	click the favorite button and   some other operations	you can add and remove authors,   as well as other common result
8		on the favorite panorama	click a publication	jump to the publication detail   page
9		on the publication detail page	click the favorite button and   some other operations	you can add and remove   publications, as well as other common result

       第二部分： Scenario/Integration Test（场景测试）: We will test whether modules which are related to each other can perform correctly.

        We will assume several user scenarios and try to deal with the assumed needs of users.

        1,a researcher would want to find the conference agenda which he wants to attend.

        2,an attendee woul like to search the agenda to find what he is interested in, and want to look further informations about it.

        3,an attendee woul also like to be reminded when his interedted topic is about to start.

        4,when a researcher is listenning to a topic at a conference, he wants to write down his thoughts and some confuses.

        5,when a researcher is searching some authors, publications as well as conferences, he would want to add them as his favorite and want to look for them more conveniently.

        第三部分：Negative Test: We will assume several unexpected situations to test whether our app can still  handle and work well.

        1,when the network is out of reach, our app can still work.

        2,when the battery is out, our app can store important informations and performe well when started next time.

        3,when many users is using this to look for the same agenda, our app would still respond in a tolerable time.

ii)    Usability Test（易用性测试）: We will test whether our app can work efficiently and effectively.

        we maybe act as users to test whether our app can respond our queries fluently and the interface is easily and friendly.

iii)    Regression Test（回归测试）: last but not the least.

       During our test, we will do regression test everyday to make sure that some passed test cases are not influenced by our bug fix. When all the bugs are fixed(maybe some are postponed to the next iteration), all team members would do this regression test, to guarantee that all the bugs are fixed and didn't recur before our release.