CSC/ECE 517 Spring 2018/E1813 Test Menu Items Model - Revision history

Kghosh: /* Testing Conditions */

2018-04-03T03:23:32Z

Testing Conditions

@@ Line 294: / Line 294: @@
       Here we expect that if the method items_for_permissions() is invoked on the MenuItems and passed the value 1 as a parameter,
       the method should return an empty list.
 The screenshot of the actual <b>menu_item_spec.rb</b> file is give below and the pull request can be found here[https://github.com/expertiza/expertiza/pull/1152]:

Kghosh: /* Test Driven-Development */

2018-04-03T03:03:12Z

Test Driven-Development

← Older revision		Revision as of 03:03, 3 April 2018
Line 10:		Line 10:
	The TDD sequence can be can be summarized in following steps.		The TDD sequence can be can be summarized in following steps.

	1.Add a Test		*1.Add a Test
	2.Run all tests and see if the new test fails		*2.Run all tests and see if the new test fails
	3.Write the code		*3.Write the code
	4.Run tests		*4.Run tests
	5. Refactor code		*5. Refactor code
	6. Repeat		*6. Repeat

	Advantages of using TDD:		Advantages of using TDD:

Kghosh: /* Test Driven-Development */

2018-04-03T03:02:01Z

Test Driven-Development

← Older revision		Revision as of 03:02, 3 April 2018
Line 10:		Line 10:
	The TDD sequence can be can be summarized in following steps.		The TDD sequence can be can be summarized in following steps.

	1.Add a Test 2.Run all tests and see if the new test fails		1.Add a Test
			2.Run all tests and see if the new test fails
	3.Write the code 4.Run tests 5. Refactor code 6. Repeat		3.Write the code
			4.Run tests
			5. Refactor code
			6. Repeat

	Advantages of using TDD:		Advantages of using TDD:

Hpullag: /* Plan Of Work */

2018-04-03T02:56:35Z

Plan Of Work

← Older revision		Revision as of 02:56, 3 April 2018
Line 68:		Line 68:
	3. Sandeep Rajendran(srajend@ncsu.edu)		3. Sandeep Rajendran(srajend@ncsu.edu)

	== Plan Of Work ==		== Plan Of Work - Test Plan ==

	The task in hand was to write test cases for testing the menu_items model file. No Rspec file for the corresponding model exists so there was a need to create a new file and build tests from scratch.		The task in hand was to write test cases for testing the menu_items model file. No Rspec file for the corresponding model exists so there was a need to create a new file and build tests from scratch.

Hpullag: /* Test Driven-Development */

2018-04-03T02:56:11Z

Test Driven-Development

← Older revision		Revision as of 02:56, 3 April 2018
Line 10:		Line 10:
	The TDD sequence can be can be summarized in following steps.		The TDD sequence can be can be summarized in following steps.

	1.Add a Test 2.Run all tests and see if the new test fails ~~3.Write the code~~		1.Add a Test 2.Run all tests and see if the new test fails

	4.Run tests 5. Refactor code 6. Repeat		3.Write the code 4.Run tests 5. Refactor code 6. Repeat

	Advantages of using TDD:		Advantages of using TDD:

Hpullag: /* Test Driven-Development */

2018-04-03T02:55:47Z

Test Driven-Development

← Older revision		Revision as of 02:55, 3 April 2018
Line 10:		Line 10:
	The TDD sequence can be can be summarized in following steps.		The TDD sequence can be can be summarized in following steps.

	1.Add a Test		1.Add a Test 2.Run all tests and see if the new test fails 3.Write the code

	~~2.Run all tests and see if the new test fails~~		4.Run tests 5. Refactor code 6. Repeat

	~~3.Write the code~~

	4.Run tests

	5. Refactor code

	6. Repeat

	Advantages of using TDD:		Advantages of using TDD:

Hpullag: /* Test Driven-Development */

2018-04-03T02:55:02Z

Test Driven-Development

← Older revision		Revision as of 02:55, 3 April 2018
Line 10:		Line 10:
	The TDD sequence can be can be summarized in following steps.		The TDD sequence can be can be summarized in following steps.

	1.Add a Test:		1.Add a Test

	2.Run all tests and see if the new test fails:		2.Run all tests and see if the new test fails

	3.Write the code:		3.Write the code

	4.Run tests:		4.Run tests

	5. Refactor code:		5. Refactor code

	6. Repeat:		6. Repeat

	Advantages of using TDD:		Advantages of using TDD:

Hpullag: /* Test Driven-Development */

2018-04-03T02:54:12Z

Test Driven-Development

← Older revision		Revision as of 02:54, 3 April 2018
Line 11:		Line 11:

	1.Add a Test:		1.Add a Test:

	TDD begins by writing succinct test cases to test each of the features. This is opposite to traditional software development paradigm where code is written first and then test cases are later written to test the application.

	2.Run all tests and see if the new test fails:		2.Run all tests and see if the new test fails:

	This step validates that the test harness is working correctly, shows that the new test does not pass without requiring new code because the required behavior already exists, and it rules out the possibility that the new test is flawed and will always pass. The new test should fail for the expected reason. This step increases the developer's confidence in the new test.

	3.Write the code:		3.Write the code:

	~~The next step is to write the minimum amount of code that causes the test case to pass.~~

	4.Run tests:		4.Run tests:

	In this steps the test cases are run.If all test cases now pass, the programmer can be confident that the new code meets the test requirements, and does not break or degrade any existing features. If they do not, the new code must be adjusted until they do.

	5. Refactor code:		5. Refactor code:

	~~In this step, refactoring of code is performed by following good design principles like removal of duplicate code, improving the readability and maintainability of the code.~~

	6. Repeat:		6. Repeat:

	~~Starting with another new test,the next step is to repeat the cycle to push the functionality forward.~~



	Advantages of using TDD:		Advantages of using TDD:

Hpullag: /* Test Entries Creation */

2018-04-03T02:42:01Z

Test Entries Creation

← Older revision		Revision as of 02:42, 3 April 2018
Line 213:		Line 213:
	Mock/dummy objects are needed to be created for any unit testing criteria.These objects are loaded freshly and deleted after every testing condition.		Mock/dummy objects are needed to be created for any unit testing criteria.These objects are loaded freshly and deleted after every testing condition.

	Several methods exist for creating such a objects, whose parameters need to be designed to satisfy the conditions under test. Using 'factories' is one such method where few of the attributes are filled in with predefined values when an created. Here, for this specific case, we haven't used, factories method as, the number of attributes were limited in menu_items model and could be filled in completely with the required values each time.		Several methods exist for creating such a objects, whose parameters need to be designed to satisfy the conditions under test. Using factories command pattern is one such method where few of the attributes are filled in with predefined values when an created. Here, for this specific case, we haven't used, factories method as, the number of attributes were limited in menu_items model and could be filled in completely with the required values each time.

	For testing menu_items, we created required entries into the database using "MenuItem.new()" method, giving different values for each of the test inputs to cover the required testing conditions.		For testing menu_items, we created required entries into the database using "MenuItem.new()" method, giving different values for each of the test inputs to cover the required testing conditions.

Hpullag: /* References */

2018-04-03T01:53:15Z

References

← Older revision		Revision as of 01:53, 3 April 2018
Line 349:		Line 349:
	#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]		#[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza project documentation wiki]
	#[https://relishapp.com/rspec Rspec Documentation]		#[https://relishapp.com/rspec Rspec Documentation]
			#[https://youtu.be/Acywhk_IjDY Screen Cast of project Running]