E1848 Write unit tests for assignment team - Revision history

Wkuang2 at 03:49, 11 November 2018

2018-11-11T03:49:55Z

← Older revision		Revision as of 03:49, 11 November 2018
Line 53:		Line 53:
	13. two test cases for method " delete and destroy": Testing delete and destory.		13. two test cases for method " delete and destroy": Testing delete and destory.

	14. ~~two~~ test ~~cases~~ for method "~~hyoerlinks~~": the ~~current teams submitted hyperlinks and not submitted the hyperlinks~~		14. one test case for method "get_first_member": Let a team have two members, the first assigned member is expected to be returned by this method.

	15.~~three~~ test cases for method "~~submit_hyperlink~~": the ~~hyperlink is empty, the hyperlink is~~ not ~~empty and it calls~~ the ~~method on NET::HTTP,the hyperlink is not empty and it raises error~~		15. two test cases for method "hyoerlinks": the current teams submitted hyperlinks and not submitted the hyperlinks

	16.three test cases for method "~~team~~": the ~~participant~~ is ~~nil~~, the ~~participant exists~~ and the ~~team user exists~~		16.three test cases for method "submit_hyperlink": the hyperlink is empty, the hyperlink is not empty and it calls the method on NET::HTTP,the hyperlink is not empty and it raises error

	17.two test cases for method "export_files": ~~the team_name equals false and true~~		17.three test cases for method "team": the participant is nil, the participant exists and the team user exists

			18.two test cases for method "export_files": an exception is expected if team is not exist or a new exported file is expected.

	==Unit Tests==		==Unit Tests==

2018-11-10T03:10:51Z

Test Plan

← Older revision		Revision as of 03:10, 10 November 2018
Line 60:		Line 60:

	17.two test cases for method "export_files": the team_name equals false and true		17.two test cases for method "export_files": the team_name equals false and true

	~~18.~~

	==Unit Tests==		==Unit Tests==

2018-11-10T03:10:10Z

Test Plan

← Older revision		Revision as of 03:10, 10 November 2018
Line 59:		Line 59:
	16.three test cases for method "team": the participant is nil, the participant exists and the team user exists		16.three test cases for method "team": the participant is nil, the participant exists and the team user exists

	17.		17.two test cases for method "export_files": the team_name equals false and true

			18.

	==Unit Tests==		==Unit Tests==

2018-11-10T03:09:04Z

Test Plan

← Older revision		Revision as of 03:09, 10 November 2018
Line 57:		Line 57:
	15.three test cases for method "submit_hyperlink": the hyperlink is empty, the hyperlink is not empty and it calls the method on NET::HTTP,the hyperlink is not empty and it raises error		15.three test cases for method "submit_hyperlink": the hyperlink is empty, the hyperlink is not empty and it calls the method on NET::HTTP,the hyperlink is not empty and it raises error

	16.		16.three test cases for method "team": the participant is nil, the participant exists and the team user exists

			17.

	==Unit Tests==		==Unit Tests==

2018-11-10T03:07:15Z

Test Plan

← Older revision		Revision as of 03:07, 10 November 2018
Line 55:		Line 55:
	14. two test cases for method "hyoerlinks": the current teams submitted hyperlinks and not submitted the hyperlinks		14. two test cases for method "hyoerlinks": the current teams submitted hyperlinks and not submitted the hyperlinks

	15.		15.three test cases for method "submit_hyperlink": the hyperlink is empty, the hyperlink is not empty and it calls the method on NET::HTTP,the hyperlink is not empty and it raises error

			16.

	==Unit Tests==		==Unit Tests==

2018-11-10T03:05:25Z

Test Plan

← Older revision		Revision as of 03:05, 10 November 2018
Line 52:		Line 52:

	13. two test cases for method " delete and destroy": Testing delete and destory.		13. two test cases for method " delete and destroy": Testing delete and destory.

			14. two test cases for method "hyoerlinks": the current teams submitted hyperlinks and not submitted the hyperlinks

			15.

	==Unit Tests==		==Unit Tests==

2018-11-10T03:03:07Z

Motivation

← Older revision		Revision as of 03:03, 10 November 2018
Line 6:		Line 6:
	====Motivation====		====Motivation====
	Make sure assignment_team.rb provides all functions as expected is important for the whole system. It requires enough tests for all the functions and the edge cases may occur. However, there are not enough unit tests for this model in expertiza. The following tests are added to assignment_team.rb in this project.		Make sure assignment_team.rb provides all functions as expected is important for the whole system. It requires enough tests for all the functions and the edge cases may occur. However, there are not enough unit tests for this model in expertiza. The following tests are added to assignment_team.rb in this project.
			To make sure we can cover as many conditions as we can(the objective for this project is getting at least 90% coverage rate), we first design test cases. The following factors are taking into considerations: the expected functions for each method, the possible edge cases and the pre-conditions for each cases. Then we get the unit test plan and complete the test following test steps.

	==Memebers of Project==		==Memebers of Project==

2018-11-10T02:54:49Z

File Involvement

← Older revision		Revision as of 02:54, 10 November 2018
Line 22:		Line 22:
	2.spec/models/assignment_team_spec.rb		2.spec/models/assignment_team_spec.rb

			3.spec/factories/factories.rb

	==Test Plan==		==Test Plan==

2018-11-10T02:52:49Z

Project Introduction

← Older revision		Revision as of 02:52, 10 November 2018
Line 2:		Line 2:

	==Project Introduction==		==Project Introduction==
	assignment_team.rb is the child class of team.rb. It is used to ~~manage student teams~~ in ~~assignments~~.		====Background====
	~~There~~ are not enough unit tests for this model in expertiza. The following tests are added to assignment_team.rb in this project.		assignment_team.rb is the child class of team.rb. It is used to handle multiple problems relates to team in the assignment. Its responsibilities can mainly fall in three categories: participant of the team, reviews of the team, and the operation for the whole team. For the participant, it can be used to decide if a participant is in a given team and view the members of the team or remove a member. For reviews, it deals with the problem that getting the reviews for the team, assign reviewer for the team and get if the team has been reviewed by a specific reviewers. For the whole team, we can delete the team or view the scores, etc. by using this class.
			====Motivation====
			Make sure assignment_team.rb provides all functions as expected is important for the whole system. It requires enough tests for all the functions and the edge cases may occur. However, there are not enough unit tests for this model in expertiza. The following tests are added to assignment_team.rb in this project.

	==Memebers of Project==		==Memebers of Project==

2018-11-10T00:50:39Z

Memeber of Project

← Older revision		Revision as of 00:50, 10 November 2018
Line 5:		Line 5:
	There are not enough unit tests for this model in expertiza. The following tests are added to assignment_team.rb in this project.		There are not enough unit tests for this model in expertiza. The following tests are added to assignment_team.rb in this project.

	==~~Memeber~~ of Project==		==Memebers of Project==
	Jianshu Zhang		Jianshu Zhang