https://wiki.expertiza.ncsu.edu/api.php?action=feedcontributions&feedformat=atom&user=Vpaul 2026-06-13T20:29:45Z User contributions MediaWiki 1.41.0 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015_E1585_Use_Ajax_for_Add_Participants,_Add_TA_,Edit_Questionnaires_Screens&diff=99923 2015-11-14T04:39:32Z

<p>Vpaul: </p> <hr /> <div>==Overall Design==<br /> ===Purpose===<br /> On some of the views, whenever a user adds or modifies an existing record, the system is saving the entire page and then reloading the entire page back. This is an inefficient way of saving, especially if only one attribute has been modified. Our goal is to modify the views and use AJAX, so that only the newly added information is saved and not the entire page.<br /> <br /> We will be altering the views for the following scenarios<br /> <br /> # Add Participants to an assignment<br /> # Edit questionnaire<br /> # Add TA to an existing course<br /> <br /> ===Scope and Documentation===<br /> Upon careful investigation, we find that the following views need to be modified<br /> <br /> # participant/list.html.erb<br /> # course/view_teaching_assistants.html.erb<br /> # questionnaires/edit.html.erb<br /> <br /> The documents that will be generated for this project are the design document, the actual files that we edit or create, and a ReadMe that explains what we did and how to use the modified product.<br /> <br /> ===AJAX===<br /> Ajax is the acronym for Asynchronous Javascript and XML. It is not a programming language or a tool but a concept. Using Ajax allows us to update parts of web page without updating the entire page. Ajax requires basic understanding of HTML and Javascript. Ajax is a client side script which communicates with a server without sharing the entire page over again. It allows web pages to be updated asynchronously by exchanging small pieces of information with the server. It is not visible to the user, but works on the back end. The general web pages which do not use Ajax, load the entire page over when part of new information is added. <br /> Applications where AJAX is used: Google Maps, Gmail, Twitter, Facebook. Ajax is very popular now, and the reason being its user friendliness, increased speed of web page updating and efficiency is increased as well.<br /> <br /> Functionality of Ajax could be understood by the following diagram:<br /> <br /> [[File:AJAX.png]]<br /> <br /> ==Interface and Testing==<br /> Our project will modify the existing views. After modification, the views’ look and feel should remain same as before. The rendering should be faster with lesser data sent to and from the server.<br /> <br /> ===To test add participants:===<br /> # Login in as instructor.<br /> # Create a new assignment and save it.<br /> # Go to Manage -&gt; Assignments, you should see your newly added assignment here.<br /> # Now click on ’Add participants’ button available in the list of actions for the assignment, which will direct you to the page which lists all the participants of an assignment. Here you will have the option to add a new participant.<br /> <br /> [[File:AssgnPart.png]]<br /> <br /> ===To test editing questionnaire===<br /> # Login in as instructor.<br /> # Go to Manage -&gt; Questionnaires. Create a new Review Questionnaire by clicking on the ‘New public item’ button for ‘Review’.<br /> # Name the Questionnaire and click on create button<br /> # Click on Edit for newly created questionnaire.<br /> <br /> [[File:Quest.png]]<br /> <br /> ===To test adding TA===<br /> # Login in as instructor.<br /> # Go to Manage -&gt; Courses, you should see the list of courses already present in the Expertiza.<br /> # Now click on ’Add TA’ button available in the list of actions for the course, which will direct you to the page which lists all the TAs of a course. Through this page, we can add new TAs as well.<br /> <br /> [[File:TA.png]]<br /> <br /> ==Assumptions==<br /> This project only modifies the way that views rendered to the user. It also demands scripting some server side code to handle the requests. We do not implement anything beyond this.<br /> <br /> ==Portability==<br /> The system is portable on windows and UNIX environment. After our modification, it can continue running on both Windows and UNIX environment.<br /> <br /> ==Details of Requirements==<br /> ===Hardware requirements===<br /> * Computing Power: The amount of computing power would be the same as the current Expertiza system.<br /> <br /> * Memory: The amount of memory would be the same as the current Expertiza system.<br /> <br /> * Disk Storage: The amount of disk storage would be the same as the current Expertiza system.<br /> <br /> * Peripherals: The peripherals would be the same as the current Expertiza system.<br /> <br /> * Network: The network would be the same as the current Expertiza system.<br /> <br /> ===Software requirements===<br /> * Operating system environment : The operating system can be either windows or UNIX based OS. Both are now used in the current Expertiza system.<br /> <br /> * Networking environment: As used in the current Expertiza system<br /> <br /> * Tools: Ruby Mines, Git<br /> <br /> ===References===<br /> <br /> 1. http://www.w3schools.com/Ajax/ajax_intro.asp<br /> <br /> 2. http://www.seguetech.com/blog/2013/03/12/what-is-ajax-and-where-is-it-used-in-technology<br /> <br /> 3. http://www.tutorialspoint.com/ajax/what_is_ajax.htm</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015_E1585_Use_Ajax_for_Add_Participants,_Add_TA_,Edit_Questionnaires_Screens&diff=99920 2015-11-14T04:36:40Z

<p>Vpaul: </p> <hr /> <div>==Overall Design==<br /> ===Purpose===<br /> On some of the views, whenever a user adds or modifies an existing record, the system is saving the entire page and then reloading the entire page back. This is an inefficient way of saving, especially if only one attribute has been modified. Our goal is to modify the views and use AJAX, so that only the newly added information is saved and not the entire page.<br /> <br /> We will be altering the views for the following scenarios<br /> <br /> # Add Participants to an assignment<br /> # Edit questionnaire<br /> # Add TA to an existing course<br /> <br /> ===Scope and Documentation===<br /> Upon careful investigation, we find that the following views need to be modified<br /> <br /> # participant/list.html.erb<br /> # course/view_teaching_assistants.html.erb<br /> # questionnaires/edit.html.erb<br /> <br /> The documents that will be generated for this project are the design document, the actual files that we edit or create, and a ReadMe that explains what we did and how to use the modified product.<br /> <br /> ===AJAX===<br /> Ajax is the acronym for Asynchronous Javascript and XML. It is not a programming language or a tool but a concept. Using Ajax allows us to update parts of web page without updating the entire page. Ajax requires basic understanding of HTML and Javascript. Ajax is a client side script which communicates with a server without sharing the entire page over again. It allows web pages to be updated asynchronously by exchanging small pieces of information with the server. It is not visible to the user, but works on the back end. The general web pages which do not use Ajax, load the entire page over when part of new information is added. <br /> Applications where AJAX is used: Google Maps, Gmail, Twitter, Facebook. Ajax is very popular now, and the reason being its user friendliness, increased speed of web page updating and efficiency is increased as well.<br /> <br /> Functionality of Ajax could be understood by the following diagram:<br /> <br /> [[File:AJAX.png]]<br /> <br /> ==Interface and Testing==<br /> Our project will modify the existing views. After modification, the views’ look and feel should remain same as before. The rendering should be faster with lesser data sent to and from the server.<br /> <br /> ===To test add participants:===<br /> # Login in as instructor.<br /> # Create a new assignment and save it.<br /> # Go to Manage -&gt; Assignments, you should see your newly added assignment here.<br /> # Now click on ’Add participants’ button available in the list of actions for the assignment, which will direct you to the page which lists all the participants of an assignment. Here you will have the option to add a new participant.<br /> <br /> [[File:AssgnPart.png]]<br /> <br /> ===To test editing questionnaire===<br /> # Login in as instructor.<br /> # Go to Manage -&gt; Questionnaires. Create a new Review Questionnaire by clicking on the ‘New public item’ button for ‘Review’.<br /> # Name the Questionnaire and click on create button<br /> # Click on Edit for newly created questionnaire.<br /> <br /> [[File:Quest.png]]<br /> <br /> ===To test adding TA===<br /> # Login in as instructor.<br /> # Go to Manage -&gt; Courses, you should see the list of courses already present in the Expertiza.<br /> # Now click on ’Add TA’ button available in the list of actions for the course, which will direct you to the page which lists all the TAs of a course. Through this page, we can add new TAs as well.<br /> <br /> [[File:TA.png]]<br /> <br /> ==Assumptions==<br /> This project only modifies the way that views rendered to the user. It also demands scripting some server side code to handle the requests. We do not implement anything beyond this.<br /> <br /> ==Portability==<br /> The system is portable on windows and UNIX environment. After our modification, it can continue running on both Windows and UNIX environment.<br /> <br /> ==Details of Requirements==<br /> ===Hardware requirements===<br /> * Computing Power: The amount of computing power would be the same as the current Expertiza system.<br /> <br /> * Memory: The amount of memory would be the same as the current Expertiza system.<br /> <br /> * Disk Storage: The amount of disk storage would be the same as the current Expertiza system.<br /> <br /> * Peripherals: The peripherals would be the same as the current Expertiza system.<br /> <br /> * Network: The network would be the same as the current Expertiza system.<br /> <br /> ===Software requirements===<br /> * Operating system environment : The operating system can be either windows or UNIX based OS. Both are now used in the current Expertiza system.<br /> <br /> * Networking environment: As used in the current Expertiza system<br /> <br /> * Tools: Ruby Mines, Git</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015_E1585_Use_Ajax_for_Add_Participants,_Add_TA_,Edit_Questionnaires_Screens&diff=99919 2015-11-14T04:36:22Z

<p>Vpaul: </p> <hr /> <div>==Overall Design==<br /> ===Purpose===<br /> On some of the views, whenever a user adds or modifies an existing record, the system is saving the entire page and then reloading the entire page back. This is an inefficient way of saving, especially if only one attribute has been modified. Our goal is to modify the views and use AJAX, so that only the newly added information is saved and not the entire page.<br /> <br /> We will be altering the views for the following scenarios<br /> <br /> # Add Participants to an assignment<br /> # Edit questionnaire<br /> # Add TA to an existing course<br /> <br /> ===Scope and Documentation===<br /> Upon careful investigation, we find that the following views need to be modified<br /> <br /> # participant/list.html.erb<br /> # course/view_teaching_assistants.html.erb<br /> # questionnaires/edit.html.erb<br /> <br /> The documents that will be generated for this project are the design document, the actual files that we edit or create, and a ReadMe that explains what we did and how to use the modified product.<br /> <br /> ===AJAX===<br /> Ajax is the acronym for Asynchronous Javascript and XML. It is not a programming language or a tool but a concept. Using Ajax allows us to update parts of web page without updating the entire page. Ajax requires basic understanding of HTML and Javascript. Ajax is a client side script which communicates with a server without sharing the entire page over again. It allows web pages to be updated asynchronously by exchanging small pieces of information with the server. It is not visible to the user, but works on the back end. The general web pages which do not use Ajax, load the entire page over when part of new information is added. <br /> Applications where AJAX is used: Google Maps, Gmail, Twitter, Facebook. Ajax is very popular now, and the reason being its user friendliness, increased speed of web page updating and efficiency is increased as well.<br /> <br /> Functionality of Ajax could be understood by the following diagram:<br /> [[File:AJAX.png]]<br /> <br /> ==Interface and Testing==<br /> Our project will modify the existing views. After modification, the views’ look and feel should remain same as before. The rendering should be faster with lesser data sent to and from the server.<br /> <br /> ===To test add participants:===<br /> # Login in as instructor.<br /> # Create a new assignment and save it.<br /> # Go to Manage -&gt; Assignments, you should see your newly added assignment here.<br /> # Now click on ’Add participants’ button available in the list of actions for the assignment, which will direct you to the page which lists all the participants of an assignment. Here you will have the option to add a new participant.<br /> <br /> [[File:AssgnPart.png]]<br /> <br /> ===To test editing questionnaire===<br /> # Login in as instructor.<br /> # Go to Manage -&gt; Questionnaires. Create a new Review Questionnaire by clicking on the ‘New public item’ button for ‘Review’.<br /> # Name the Questionnaire and click on create button<br /> # Click on Edit for newly created questionnaire.<br /> <br /> [[File:Quest.png]]<br /> <br /> ===To test adding TA===<br /> # Login in as instructor.<br /> # Go to Manage -&gt; Courses, you should see the list of courses already present in the Expertiza.<br /> # Now click on ’Add TA’ button available in the list of actions for the course, which will direct you to the page which lists all the TAs of a course. Through this page, we can add new TAs as well.<br /> <br /> [[File:TA.png]]<br /> <br /> ==Assumptions==<br /> This project only modifies the way that views rendered to the user. It also demands scripting some server side code to handle the requests. We do not implement anything beyond this.<br /> <br /> ==Portability==<br /> The system is portable on windows and UNIX environment. After our modification, it can continue running on both Windows and UNIX environment.<br /> <br /> ==Details of Requirements==<br /> ===Hardware requirements===<br /> * Computing Power: The amount of computing power would be the same as the current Expertiza system.<br /> <br /> * Memory: The amount of memory would be the same as the current Expertiza system.<br /> <br /> * Disk Storage: The amount of disk storage would be the same as the current Expertiza system.<br /> <br /> * Peripherals: The peripherals would be the same as the current Expertiza system.<br /> <br /> * Network: The network would be the same as the current Expertiza system.<br /> <br /> ===Software requirements===<br /> * Operating system environment : The operating system can be either windows or UNIX based OS. Both are now used in the current Expertiza system.<br /> <br /> * Networking environment: As used in the current Expertiza system<br /> <br /> * Tools: Ruby Mines, Git</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=File:AJAX.png&diff=99918 2015-11-14T04:35:31Z

<p>Vpaul: </p> <hr /> <div></div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015_E1585_Use_Ajax_for_Add_Participants,_Add_TA_,Edit_Questionnaires_Screens&diff=99917 2015-11-14T04:35:03Z

<p>Vpaul: </p> <hr /> <div>==Overall Design==<br /> ===Purpose===<br /> On some of the views, whenever a user adds or modifies an existing record, the system is saving the entire page and then reloading the entire page back. This is an inefficient way of saving, especially if only one attribute has been modified. Our goal is to modify the views and use AJAX, so that only the newly added information is saved and not the entire page.<br /> <br /> We will be altering the views for the following scenarios<br /> <br /> # Add Participants to an assignment<br /> # Edit questionnaire<br /> # Add TA to an existing course<br /> <br /> ===Scope and Documentation===<br /> Upon careful investigation, we find that the following views need to be modified<br /> <br /> # participant/list.html.erb<br /> # course/view_teaching_assistants.html.erb<br /> # questionnaires/edit.html.erb<br /> <br /> The documents that will be generated for this project are the design document, the actual files that we edit or create, and a ReadMe that explains what we did and how to use the modified product.<br /> <br /> ===AJAX===<br /> Ajax is the acronym for Asynchronous Javascript and XML. It is not a programming language or a tool but a concept. Using Ajax allows us to update parts of web page without updating the entire page. Ajax requires basic understanding of HTML and Javascript. Ajax is a client side script which communicates with a server without sharing the entire page over again. It allows web pages to be updated asynchronously by exchanging small pieces of information with the server. It is not visible to the user, but works on the back end. The general web pages which do not use Ajax, load the entire page over when part of new information is added. <br /> Applications where AJAX is used: Google Maps, Gmail, Twitter, Facebook. Ajax is very popular now, and the reason being its user friendliness, increased speed of web page updating and efficiency is increased as well.<br /> <br /> <br /> ==Interface and Testing==<br /> Our project will modify the existing views. After modification, the views’ look and feel should remain same as before. The rendering should be faster with lesser data sent to and from the server.<br /> <br /> ===To test add participants:===<br /> # Login in as instructor.<br /> # Create a new assignment and save it.<br /> # Go to Manage -&gt; Assignments, you should see your newly added assignment here.<br /> # Now click on ’Add participants’ button available in the list of actions for the assignment, which will direct you to the page which lists all the participants of an assignment. Here you will have the option to add a new participant.<br /> <br /> [[File:AssgnPart.png]]<br /> <br /> ===To test editing questionnaire===<br /> # Login in as instructor.<br /> # Go to Manage -&gt; Questionnaires. Create a new Review Questionnaire by clicking on the ‘New public item’ button for ‘Review’.<br /> # Name the Questionnaire and click on create button<br /> # Click on Edit for newly created questionnaire.<br /> <br /> [[File:Quest.png]]<br /> <br /> ===To test adding TA===<br /> # Login in as instructor.<br /> # Go to Manage -&gt; Courses, you should see the list of courses already present in the Expertiza.<br /> # Now click on ’Add TA’ button available in the list of actions for the course, which will direct you to the page which lists all the TAs of a course. Through this page, we can add new TAs as well.<br /> <br /> [[File:TA.png]]<br /> <br /> ==Assumptions==<br /> This project only modifies the way that views rendered to the user. It also demands scripting some server side code to handle the requests. We do not implement anything beyond this.<br /> <br /> ==Portability==<br /> The system is portable on windows and UNIX environment. After our modification, it can continue running on both Windows and UNIX environment.<br /> <br /> ==Details of Requirements==<br /> ===Hardware requirements===<br /> * Computing Power: The amount of computing power would be the same as the current Expertiza system.<br /> <br /> * Memory: The amount of memory would be the same as the current Expertiza system.<br /> <br /> * Disk Storage: The amount of disk storage would be the same as the current Expertiza system.<br /> <br /> * Peripherals: The peripherals would be the same as the current Expertiza system.<br /> <br /> * Network: The network would be the same as the current Expertiza system.<br /> <br /> ===Software requirements===<br /> * Operating system environment : The operating system can be either windows or UNIX based OS. Both are now used in the current Expertiza system.<br /> <br /> * Networking environment: As used in the current Expertiza system<br /> <br /> * Tools: Ruby Mines, Git</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015_E1585_Use_Ajax_for_Add_Participants,_Add_TA_,Edit_Questionnaires_Screens&diff=99190 2015-11-09T22:39:48Z

<p>Vpaul: /* Assumptions */</p> <hr /> <div>==Overall Design==<br /> ===Purpose===<br /> On some of the views, whenever a user adds or modifies an existing record, the system is saving the entire page and then reloading the entire page back. This is an inefficient way of saving, especially if only one attribute has been modified. Our goal is to modify the views and use AJAX, so that only the newly added information is saved and not the entire page.<br /> <br /> We will be altering the views for the following scenarios<br /> <br /> # Add Participants to an assignment<br /> # Edit questionnaire<br /> # Add TA to an existing course<br /> <br /> ===Scope and Documentation===<br /> Upon careful investigation, we find that the following views need to be modified<br /> <br /> # participant/list.html.erb<br /> # course/view_teaching_assistants.html.erb<br /> # questionnaires/edit.html.erb<br /> <br /> The documents that will be generated for this project are the design document, the actual files that we edit or create, and a ReadMe that explains what we did and how to use the modified product.<br /> <br /> ==Interface and Testing==<br /> Our project will modify the existing views. After modification, the views’ look and feel should remain same as before. The rendering should be faster with lesser data sent to and from the server.<br /> <br /> ===To test add participants:===<br /> # Login in as instructor.<br /> # Create a new assignment and save it.<br /> # Go to Manage -&gt; Assignments, you should see your newly added assignment here.<br /> # Now click on ’Add participants’ button available in the list of actions for the assignment, which will direct you to the page which lists all the participants of an assignment. Here you will have the option to add a new participant.<br /> <br /> ===To test editing questionnaire===<br /> # Login in as instructor.<br /> # Go to Manage -&gt; Questionnaires. Create a new Review Questionnaire by clicking on the ‘New public item’ button for ‘Review’.<br /> # Name the Questionnaire and click on create button<br /> # Click on Edit for newly created questionnaire.<br /> <br /> ===To test adding TA===<br /> # Login in as instructor.<br /> # Go to Manage -&gt; Courses, you should see the list of courses already present in the Expertiza.<br /> # Now click on ’Add TA’ button available in the list of actions for the course, which will direct you to the page which lists all the TAs of a course. Through this page, we can add new TAs as well.<br /> <br /> ==Assumptions==<br /> This project only modifies the way that views rendered to the user. It also demands scripting some server side code to handle the requests. We do not implement anything beyond this.<br /> <br /> ==Portability==<br /> The system is portable on windows and UNIX environment. After our modification, it can continue running on both Windows and UNIX environment.<br /> <br /> ==Details of Requirements==<br /> ===Hardware requirements===<br /> * Computing Power: The amount of computing power would be the same as the current Expertiza system.<br /> <br /> * Memory: The amount of memory would be the same as the current Expertiza system.<br /> <br /> * Disk Storage: The amount of disk storage would be the same as the current Expertiza system.<br /> <br /> * Peripherals: The peripherals would be the same as the current Expertiza system.<br /> <br /> * Network: The network would be the same as the current Expertiza system.<br /> <br /> ===Software requirements===<br /> * Operating system environment : The operating system can be either windows or UNIX based OS. Both are now used in the current Expertiza system.<br /> <br /> * Networking environment: As used in the current Expertiza system<br /> <br /> * Tools: Ruby Mines, Git</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=98754 2015-11-07T15:04:48Z

<p>Vpaul: /* Running the tests */</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [https://github.com/gmeneze/expertiza Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [https://www.youtube.com/watch?v=yC_heDL6GSw Youtube video manual]<br /> <br /> ==Reviewer Instructions==<br /> ===Clone the reopsitory===<br /> Visit [https://github.com/gmeneze/expertiza Github repo] for the repository URL. Make sure you're logged in if you have commit access, because the URL will be different.<br /> <br /> git clone (repository URL)<br /> <br /> See https://help.github.com for help on setting up git, authenticating with SSH keys, and checking out a repository.<br /> <br /> ===Installing Gems (ruby dependencies)===<br /> In the expertiza directory:<br /> <br /> bundle install<br /> <br /> ===Set up databses===<br /> *Go to the expertiza directory.<br /> <br /> cd expertiza<br /> <br /> *Create the development and test databases.<br /> <br /> rake db:create:all<br /> <br /> *If available, import the database dump that you received in class to pre-populate your database. eg:<br /> <br /> mysql -u root expertiza_development &lt; expertiza-scrubbed.sql<br /> <br /> *Run the Expertiza database migrations. This should populate your database with the current tables of the schema.<br /> <br /> rake db:migrate<br /> <br /> ===Running the tests===<br /> *Go to the expertiza directory if you are not already there.<br /> <br /> *Run the test<br /> <br /> rspec spec/features/assignment_creation_spec.rb<br /> <br /> '''Note''' : As our project involves implementation of feature tests for assignment creation rather than refactoring, we do not test the new code via UI (as the new code added are themselves tests).<br /> <br /> '''Note''' : Travis CI build fails because we are directly using the development database for our tests, thus Travis CI is not able to locate the login information. This was done because it was not possible to create factories or fixtures for our tests. So, please don’t consider the build failure in the pull request to be a valid error.<br /> <br /> ==Solutions to problems while setting up the repository==<br /> ===rjb gem error===<br /> * To solve this, make sure that you have java installed on your system or else you could do that from [https://help.ubuntu.com/community/Java here].<br /> * Then set the JAVA_HOME environment variable by typing this on the terminal<br /> <br /> export JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64<br /> <br /> * Run bundle install again.<br /> <br /> ===pg gem error===<br /> * To solve this, we have to install PostgreSQL.<br /> * Then type in the following set of commands in the terminal<br /> <br /> sudo sh -c &quot;echo 'deb http://apt.postgresql.org/pub/repos/apt/ precise-pgdg main' &gt; /etc/apt/sources.list.d/pgdg.list&quot;<br /> wget --quiet -O - http://apt.postgresql.org/pub/repos/apt/ACCC4CF8.asc | sudo apt-key add -<br /> sudo apt-get update<br /> sudo apt-get install postgresql-common<br /> sudo apt-get install postgresql-9.3 libpq-dev<br /> <br /> *Run bundle install again<br /> <br /> ===Database related errors===<br /> * Here is the link of Expertiza scrubbed DB (https://drive.google.com/a/ncsu.edu/file/d/0B2vDvVjH76uESEkzSWpJRnhGbmc/view?usp=sharing)<br /> * Download the file, unzip it and dump to MySQL.<br /> * Then type<br /> <br /> rake db:migrate RAILS_ENV=development<br /> rake db:migrate RAILS_ENV=test<br /> <br /> ===Other errors===<br /> For any other kind of errors faced during setting up the repository, you can write to us at any of the following ids.<br /> <br /> * aslingwa@ncsu.edu<br /> * gmeneze@ncsu.edu<br /> * vpaul@ncsu.edu<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. One of the major reasons for selecting Capybara to write our tests was that it has an intuitive API which mimics the language an actual user would use and also we can run tests from fast headless mode to an actual browser with no changes to our tests.<br /> <br /> ==Scenarios Tested==<br /> No matter which combination of parameters are selected in the creation of the assignment, the test cases should pass. Following are some of the scenarios which we have tested.<br /> <br /> ===Scenarios for private assignment=== <br /> *Create Assignment with Has teams parameter<br /> *Create Assignment with Has quiz parameter<br /> *Create Assignment with Wiki assignment parameter<br /> *Create Assignment with Micro-task assignment parameter<br /> *Create Assignment with Reviews visible to all other reviewers parameter<br /> *Create Assignment with Is code submission required parameter<br /> *Create Assignment with Available to students parameter<br /> *Create Assignment with all options<br /> *Create Assignment with no options<br /> *Create Assignment with Has teams and Has quiz parameters<br /> *Create Assignment with Micro-task assignment and Reviews visible to all other reviewers parameters<br /> *Create Assignment with Is code submission required and Available to students parameters<br /> *Create Assignment with Has team, Has quiz and Wiki assignment parameters<br /> *Create Assignment with negative scenario<br /> <br /> ===Scenarios for public assignment===<br /> *Create Assignment with has teams parameter<br /> *Create Assignment with has quiz parameter<br /> *Create Assignment with has Wiki Assignment parameter<br /> *Create Assignment with has Micro-task assignment parameter<br /> *Create Assignment with has Reviews visible to all other reviewers parameter<br /> *Create Assignment with has Is code submission required parameter<br /> <br /> ==Flow of our test==<br /> [[File:test flow.png]]<br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=98668 2015-11-07T02:31:44Z

<p>Vpaul: /* Scenarios Tested */</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [https://github.com/gmeneze/expertiza Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [https://www.youtube.com/watch?v=yC_heDL6GSw Youtube video manual]<br /> <br /> ==Reviewer Instructions==<br /> ===Clone the reopsitory===<br /> Visit [https://github.com/gmeneze/expertiza Github repo] for the repository URL. Make sure you're logged in if you have commit access, because the URL will be different.<br /> <br /> git clone (repository URL)<br /> <br /> See https://help.github.com for help on setting up git, authenticating with SSH keys, and checking out a repository.<br /> <br /> ===Installing Gems (ruby dependencies)===<br /> In the expertiza directory:<br /> <br /> bundle install<br /> <br /> ===Set up databses===<br /> *Go to the expertiza directory.<br /> <br /> cd expertiza<br /> <br /> *Create the development and test databases.<br /> <br /> rake db:create:all<br /> <br /> *If available, import the database dump that you received in class to pre-populate your database. eg:<br /> <br /> mysql -u root expertiza_development &lt; expertiza-scrubbed.sql<br /> <br /> *Run the Expertiza database migrations. This should populate your database with the current tables of the schema.<br /> <br /> rake db:migrate<br /> <br /> ===Running the tests===<br /> *Go to the expertiza directory if you are not already there.<br /> <br /> *Run the test<br /> <br /> rspec spec/features/assignment_creation_spec.rb<br /> <br /> '''Note''' : As our project involves implementation of feature tests for assignment creation rather than refactoring, we do not test the new code via UI (as the new code added are themselves tests).<br /> <br /> ==Solutions to problems while setting up the repository==<br /> ===rjb gem error===<br /> * To solve this, make sure that you have java installed on your system or else you could do that from [https://help.ubuntu.com/community/Java here].<br /> * Then set the JAVA_HOME environment variable by typing this on the terminal<br /> <br /> export JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64<br /> <br /> * Run bundle install again.<br /> <br /> ===pg gem error===<br /> * To solve this, we have to install PostgreSQL.<br /> * Then type in the following set of commands in the terminal<br /> <br /> sudo sh -c &quot;echo 'deb http://apt.postgresql.org/pub/repos/apt/ precise-pgdg main' &gt; /etc/apt/sources.list.d/pgdg.list&quot;<br /> wget --quiet -O - http://apt.postgresql.org/pub/repos/apt/ACCC4CF8.asc | sudo apt-key add -<br /> sudo apt-get update<br /> sudo apt-get install postgresql-common<br /> sudo apt-get install postgresql-9.3 libpq-dev<br /> <br /> *Run bundle install again<br /> <br /> ===Database related errors===<br /> * Here is the link of Expertiza scrubbed DB (https://drive.google.com/a/ncsu.edu/file/d/0B2vDvVjH76uESEkzSWpJRnhGbmc/view?usp=sharing)<br /> * Download the file, unzip it and dump to MySQL.<br /> * Then type<br /> <br /> rake db:migrate RAILS_ENV=development<br /> rake db:migrate RAILS_ENV=test<br /> <br /> ===Other errors===<br /> For any other kind of errors faced during setting up the repository, you can write to us at any of the following ids.<br /> <br /> * aslingwa@ncsu.edu<br /> * gmeneze@ncsu.edu<br /> * vpaul@ncsu.edu<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. One of the major reasons for selecting Capybara to write our tests was that it has an intuitive API which mimics the language an actual user would use and also we can run tests from fast headless mode to an actual browser with no changes to our tests.<br /> <br /> ==Scenarios Tested==<br /> No matter which combination of parameters are selected in the creation of the assignment, the test cases should pass. Following are some of the scenarios which we have tested.<br /> <br /> ===Scenarios for private assignment=== <br /> *Create Assignment with Has teams parameter<br /> *Create Assignment with Has quiz parameter<br /> *Create Assignment with Wiki assignment parameter<br /> *Create Assignment with Micro-task assignment parameter<br /> *Create Assignment with Reviews visible to all other reviewers parameter<br /> *Create Assignment with Is code submission required parameter<br /> *Create Assignment with Available to students parameter<br /> *Create Assignment with all options<br /> *Create Assignment with no options<br /> *Create Assignment with Has teams and Has quiz parameters<br /> *Create Assignment with Micro-task assignment and Reviews visible to all other reviewers parameters<br /> *Create Assignment with Is code submission required and Available to students parameters<br /> *Create Assignment with Has team, Has quiz and Wiki assignment parameters<br /> *Create Assignment with negative scenario<br /> <br /> ===Scenarios for public assignment===<br /> *Create Assignment with has teams parameter<br /> *Create Assignment with has quiz parameter<br /> *Create Assignment with has Wiki Assignment parameter<br /> *Create Assignment with has Micro-task assignment parameter<br /> *Create Assignment with has Reviews visible to all other reviewers parameter<br /> *Create Assignment with has Is code submission required parameter<br /> <br /> ==Flow of our test==<br /> [[File:test flow.png]]<br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=98667 2015-11-07T02:27:47Z

<p>Vpaul: </p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [https://github.com/gmeneze/expertiza Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [https://www.youtube.com/watch?v=yC_heDL6GSw Youtube video manual]<br /> <br /> ==Reviewer Instructions==<br /> ===Clone the reopsitory===<br /> Visit [https://github.com/gmeneze/expertiza Github repo] for the repository URL. Make sure you're logged in if you have commit access, because the URL will be different.<br /> <br /> git clone (repository URL)<br /> <br /> See https://help.github.com for help on setting up git, authenticating with SSH keys, and checking out a repository.<br /> <br /> ===Installing Gems (ruby dependencies)===<br /> In the expertiza directory:<br /> <br /> bundle install<br /> <br /> ===Set up databses===<br /> *Go to the expertiza directory.<br /> <br /> cd expertiza<br /> <br /> *Create the development and test databases.<br /> <br /> rake db:create:all<br /> <br /> *If available, import the database dump that you received in class to pre-populate your database. eg:<br /> <br /> mysql -u root expertiza_development &lt; expertiza-scrubbed.sql<br /> <br /> *Run the Expertiza database migrations. This should populate your database with the current tables of the schema.<br /> <br /> rake db:migrate<br /> <br /> ===Running the tests===<br /> *Go to the expertiza directory if you are not already there.<br /> <br /> *Run the test<br /> <br /> rspec spec/features/assignment_creation_spec.rb<br /> <br /> '''Note''' : As our project involves implementation of feature tests for assignment creation rather than refactoring, we do not test the new code via UI (as the new code added are themselves tests).<br /> <br /> ==Solutions to problems while setting up the repository==<br /> ===rjb gem error===<br /> * To solve this, make sure that you have java installed on your system or else you could do that from [https://help.ubuntu.com/community/Java here].<br /> * Then set the JAVA_HOME environment variable by typing this on the terminal<br /> <br /> export JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64<br /> <br /> * Run bundle install again.<br /> <br /> ===pg gem error===<br /> * To solve this, we have to install PostgreSQL.<br /> * Then type in the following set of commands in the terminal<br /> <br /> sudo sh -c &quot;echo 'deb http://apt.postgresql.org/pub/repos/apt/ precise-pgdg main' &gt; /etc/apt/sources.list.d/pgdg.list&quot;<br /> wget --quiet -O - http://apt.postgresql.org/pub/repos/apt/ACCC4CF8.asc | sudo apt-key add -<br /> sudo apt-get update<br /> sudo apt-get install postgresql-common<br /> sudo apt-get install postgresql-9.3 libpq-dev<br /> <br /> *Run bundle install again<br /> <br /> ===Database related errors===<br /> * Here is the link of Expertiza scrubbed DB (https://drive.google.com/a/ncsu.edu/file/d/0B2vDvVjH76uESEkzSWpJRnhGbmc/view?usp=sharing)<br /> * Download the file, unzip it and dump to MySQL.<br /> * Then type<br /> <br /> rake db:migrate RAILS_ENV=development<br /> rake db:migrate RAILS_ENV=test<br /> <br /> ===Other errors===<br /> For any other kind of errors faced during setting up the repository, you can write to us at any of the following ids.<br /> <br /> * aslingwa@ncsu.edu<br /> * gmeneze@ncsu.edu<br /> * vpaul@ncsu.edu<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. One of the major reasons for selecting Capybara to write our tests was that it has an intuitive API which mimics the language an actual user would use and also we can run tests from fast headless mode to an actual browser with no changes to our tests.<br /> <br /> ==Scenarios Tested==<br /> ===Scenarios for private assignment=== <br /> *Create Assignment with Has teams parameter<br /> *Create Assignment with Has quiz parameter<br /> *Create Assignment with Wiki assignment parameter<br /> *Create Assignment with Micro-task assignment parameter<br /> *Create Assignment with Reviews visible to all other reviewers parameter<br /> *Create Assignment with Is code submission required parameter<br /> *Create Assignment with Available to students parameter<br /> *Create Assignment with all options<br /> *Create Assignment with no options<br /> *Create Assignment with Has teams and Has quiz parameters<br /> *Create Assignment with Micro-task assignment and Reviews visible to all other reviewers parameters<br /> *Create Assignment with Is code submission required and Available to students parameters<br /> *Create Assignment with Has team, Has quiz and Wiki assignment parameters<br /> *Create Assignment with negative scenario<br /> <br /> ===Scenarios for public assignment===<br /> *Create Assignment with has teams parameter<br /> *Create Assignment with has quiz parameter<br /> *Create Assignment with has Wiki Assignment parameter<br /> *Create Assignment with has Micro-task assignment parameter<br /> *Create Assignment with has Reviews visible to all other reviewers parameter<br /> *Create Assignment with has Is code submission required parameter<br /> <br /> ==Flow of our test==<br /> [[File:test flow.png]]<br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=98656 2015-11-07T02:07:36Z

<p>Vpaul: /* Running the tests */</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [https://github.com/gmeneze/expertiza Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [https://www.youtube.com/watch?v=yC_heDL6GSw Youtube video manual]<br /> <br /> ==Reviewer Instructions==<br /> ===Clone the reopsitory===<br /> Visit [https://github.com/gmeneze/expertiza Github repo] for the repository URL. Make sure you're logged in if you have commit access, because the URL will be different.<br /> <br /> git clone (repository URL)<br /> <br /> See https://help.github.com for help on setting up git, authenticating with SSH keys, and checking out a repository.<br /> <br /> ===Installing Gems (ruby dependencies)===<br /> In the expertiza directory:<br /> <br /> bundle install<br /> <br /> ===Set up databses===<br /> *Go to the expertiza directory.<br /> <br /> cd expertiza<br /> <br /> *Create the development and test databases.<br /> <br /> rake db:create:all<br /> <br /> *If available, import the database dump that you received in class to pre-populate your database. eg:<br /> <br /> mysql -u root expertiza_development &lt; expertiza-scrubbed.sql<br /> <br /> *Run the Expertiza database migrations. This should populate your database with the current tables of the schema.<br /> <br /> rake db:migrate<br /> <br /> ===Running the tests===<br /> *Go to the expertiza directory if you are not already there.<br /> <br /> *Run the test<br /> <br /> rspec spec/features/assignment_creation_spec.rb<br /> <br /> '''Note''' : As our project involves implementation of feature tests for assignment creation rather than refactoring, we do not test the new code via UI (as the new code added are themselves tests).<br /> <br /> ==Solutions to problems while setting up the repository==<br /> ===rjb gem error===<br /> * To solve this, make sure that you have java installed on your system or else you could do that from [https://help.ubuntu.com/community/Java here].<br /> * Then set the JAVA_HOME environment variable by typing this on the terminal<br /> <br /> export JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64<br /> <br /> * Run bundle install again.<br /> <br /> ===pg gem error===<br /> * To solve this, we have to install PostgreSQL.<br /> * Then type in the following set of commands in the terminal<br /> <br /> sudo sh -c &quot;echo 'deb http://apt.postgresql.org/pub/repos/apt/ precise-pgdg main' &gt; /etc/apt/sources.list.d/pgdg.list&quot;<br /> wget --quiet -O - http://apt.postgresql.org/pub/repos/apt/ACCC4CF8.asc | sudo apt-key add -<br /> sudo apt-get update<br /> sudo apt-get install postgresql-common<br /> sudo apt-get install postgresql-9.3 libpq-dev<br /> <br /> *Run bundle install again<br /> <br /> ===Database related errors===<br /> * Here is the link of Expertiza scrubbed DB (https://drive.google.com/a/ncsu.edu/file/d/0B2vDvVjH76uESEkzSWpJRnhGbmc/view?usp=sharing)<br /> * Download the file, unzip it and dump to MySQL.<br /> * Then type<br /> <br /> rake db:migrate RAILS_ENV=development<br /> rake db:migrate RAILS_ENV=test<br /> <br /> ===Other errors===<br /> For any other kind of errors faced during setting up the repository, you can write to us at any of the following ids.<br /> <br /> * aslingwa@ncsu.edu<br /> * gmeneze@ncsu.edu<br /> * vpaul@ncsu.edu<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. One of the major reasons for selecting Capybara to write our tests was that it has an intuitive API which mimics the language an actual user would use and also we can run tests from fast headless mode to an actual browser with no changes to our tests.<br /> <br /> ==Flow of our test==<br /> [[File:test flow.png]]<br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015_E1585_Use_Ajax_for_Add_Participants,_Add_TA_,Edit_Questionnaires_Screens&diff=98440 2015-11-06T20:26:59Z

<p>Vpaul: </p> <hr /> <div>==Overall Design==<br /> ===Purpose===<br /> On some of the views, whenever a user adds or modifies an existing record, the system is saving the entire page and then reloading the entire page back. This is an inefficient way of saving, especially if only one attribute has been modified. Our goal is to modify the views and use AJAX, so that only the newly added information is saved and not the entire page.<br /> <br /> We will be altering the views for the following scenarios<br /> <br /> # Add Participants to an assignment<br /> # Edit questionnaire<br /> # Add TA to an existing course<br /> <br /> ===Scope and Documentation===<br /> Upon careful investigation, we find that the following views need to be modified<br /> <br /> # participant/list.html.erb<br /> # course/view_teaching_assistants.html.erb<br /> # questionnaires/edit.html.erb<br /> <br /> The documents that will be generated for this project are the design document, the actual files that we edit or create, and a ReadMe that explains what we did and how to use the modified product.<br /> <br /> ==Interface and Testing==<br /> Our project will modify the existing views. After modification, the views’ look and feel should remain same as before. The rendering should be faster with lesser data sent to and from the server.<br /> <br /> ===To test add participants:===<br /> # Login in as instructor.<br /> # Create a new assignment and save it.<br /> # Go to Manage -&gt; Assignments, you should see your newly added assignment here.<br /> # Now click on ’Add participants’ button available in the list of actions for the assignment, which will direct you to the page which lists all the participants of an assignment. Here you will have the option to add a new participant.<br /> <br /> ===To test editing questionnaire===<br /> # Login in as instructor.<br /> # Go to Manage -&gt; Questionnaires. Create a new Review Questionnaire by clicking on the ‘New public item’ button for ‘Review’.<br /> # Name the Questionnaire and click on create button<br /> # Click on Edit for newly created questionnaire.<br /> <br /> ===To test adding TA===<br /> # Login in as instructor.<br /> # Go to Manage -&gt; Courses, you should see the list of courses already present in the Expertiza.<br /> # Now click on ’Add TA’ button available in the list of actions for the course, which will direct you to the page which lists all the TAs of a course. Through this page, we can add new TAs as well.<br /> <br /> ==Assumptions==<br /> This project only modifies the way that views rendered to the user. We do not implement anything beyond this.<br /> <br /> ==Portability==<br /> The system is portable on windows and UNIX environment. After our modification, it can continue running on both Windows and UNIX environment.<br /> <br /> ==Details of Requirements==<br /> ===Hardware requirements===<br /> * Computing Power: The amount of computing power would be the same as the current Expertiza system.<br /> <br /> * Memory: The amount of memory would be the same as the current Expertiza system.<br /> <br /> * Disk Storage: The amount of disk storage would be the same as the current Expertiza system.<br /> <br /> * Peripherals: The peripherals would be the same as the current Expertiza system.<br /> <br /> * Network: The network would be the same as the current Expertiza system.<br /> <br /> ===Software requirements===<br /> * Operating system environment : The operating system can be either windows or UNIX based OS. Both are now used in the current Expertiza system.<br /> <br /> * Networking environment: As used in the current Expertiza system<br /> <br /> * Tools: Ruby Mines, Git</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015_E1585_Use_Ajax_for_Add_Participants,_Add_TA_,Edit_Questionnaires_Screens&diff=98439 2015-11-06T20:14:22Z

<p>Vpaul: /* Overall Design */</p> <hr /> <div>==Overall Design==<br /> ===Purpose===<br /> On some of the views, whenever a user adds or modifies an existing record, the system is saving the entire page and then reloading the entire page back. This is an inefficient way of saving, especially if only one attribute has been modified. Our goal is to modify the views and use AJAX, so that only the newly added information is saved and not the entire page.<br /> <br /> We will be altering the views for the following scenarios<br /> <br /> # Add Participants to an assignment<br /> # Edit questionnaire<br /> # Add TA to an existing course<br /> <br /> ===Scope and Documentation===<br /> Upon careful investigation, we find that the following views need to be modified<br /> <br /> # participant/list.html.erb<br /> # course/view_teaching_assistants.html.erb<br /> # questionnaires/edit.html.erb<br /> <br /> The documents that will be generated for this project are the design document, the actual files that we edit or create, and a ReadMe that explains what we did and how to use the modified product.<br /> <br /> ==Interface and Testing==<br /> Our project will modify the existing views. After modification, the views’ look and feel should remain same as before. The rendering should be faster with lesser data sent to and from the server.<br /> <br /> ===To test add participants:===<br /> # Login in as instructor.<br /> # Create a new assignment and save it.<br /> # Go to Manage -&gt; Assignments, you should see your newly added assignment here.<br /> # Now click on ’Add participants’ button available in the list of actions for the assignment, which will direct you to the page which lists all the participants of an assignment. Here you will have the option to add a new participant.<br /> <br /> ===To test editing questionnaire===<br /> # Login in as instructor.<br /> # Go to Manage -&gt; Questionnaires. Create a new Review Questionnaire by clicking on the ‘New public item’ button for ‘Review’.<br /> # Name the Questionnaire and click on create button<br /> # Click on Edit for newly created questionnaire.<br /> <br /> ===To test adding TA===<br /> # Login in as instructor.<br /> # Go to Manage -&gt; Courses, you should see the list of courses already present in the Expertiza.<br /> # Now click on ’Add TA’ button available in the list of actions for the course, which will direct you to the page which lists all the TAs of a course. Through this page, we can add new TAs as well.</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015_E1585_Use_Ajax_for_Add_Participants,_Add_TA_,Edit_Questionnaires_Screens&diff=98437 2015-11-06T20:06:15Z

<p>Vpaul: /* Purpose */</p> <hr /> <div>==Overall Design==<br /> ===Purpose===<br /> On some of the views, whenever a user adds or modifies an existing record, the system is saving the entire page and then reloading the entire page back. This is an inefficient way of saving, especially if only one attribute has been modified. Our goal is to modify the views and use AJAX, so that only the newly added information is saved and not the entire page.<br /> <br /> We will be altering the views for the following scenarios<br /> <br /> # Add Participants to an assignment<br /> # Edit questionnaire<br /> # Add TA to an existing course</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015_E1585_Use_Ajax_for_Add_Participants,_Add_TA_,Edit_Questionnaires_Screens&diff=98436 2015-11-06T20:05:57Z

<p>Vpaul: /* Purpose */</p> <hr /> <div>==Overall Design==<br /> ===Purpose===<br /> On some of the views, whenever a user adds or modifies an existing record, the system is saving the entire page and then reloading the entire page back. This is an inefficient way of saving, especially if only one attribute has been modified. Our goal is to modify the views and use AJAX, so that only the newly added information is saved and not the entire page.<br /> <br /> We will be altering the views for the following scenarios<br /> <br /> # Add Participants to an assignment<br /> ## Edit questionnaire<br /> ### Add TA to an existing course</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015_E1585_Use_Ajax_for_Add_Participants,_Add_TA_,Edit_Questionnaires_Screens&diff=98435 2015-11-06T20:05:32Z

<p>Vpaul: Created page with &quot;==Overall Design== ===Purpose=== On some of the views, whenever a user adds or modifies an existing record, the system is saving the entire page and then reloading the entire pag...&quot;</p> <hr /> <div>==Overall Design==<br /> ===Purpose===<br /> On some of the views, whenever a user adds or modifies an existing record, the system is saving the entire page and then reloading the entire page back. This is an inefficient way of saving, especially if only one attribute has been modified. Our goal is to modify the views and use AJAX, so that only the newly added information is saved and not the entire page.<br /> <br /> We will be altering the views for the following scenarios<br /> <br /> * Add Participants to an assignment<br /> ** Edit questionnaire<br /> *** Add TA to an existing course</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015&diff=98430 2015-11-06T19:57:18Z

<p>Vpaul: /* Final Project Design Document */</p> <hr /> <div>==Writing Assignment 2==<br /> *[[CSC/ECE_517_Fall_2015/sample_page]]<br /> *[[CSC/ECE_517_Fall_2015/ossE1558BGJ]]<br /> *[[CSC/ECE 517 Fall 2015/oss/M1502/AAAASS]]<br /> *[[CSC/ECE 517 Fall 2015/oss/M1503/IntegrateXMLParser]]<br /> *[[CSC/ECE_517_Fall_2015/ossE1568BZHXJS]]<br /> *[[CSC/ECE_517_Fall_2015/ossE1572VGA]]<br /> *[[CSC/ECE_517_Fall_2015/oss_E1573_sap]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1559 rrz]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1570 avr]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1556 CHM]]<br /> *[[CSC/ECE 517 Fall 2015/oss M1504 JJD]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1562 APS]]<br /> *[[CSC/ECE 517 Fall 2015/oss M1501 GSN]]<br /> *[[CSC/ECE 517 Fall 2015/oss M1501 GSN]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1550 KMM]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1551 RGS]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1555 GMR]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1552 NFR]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1565 AAJ]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1561 WZL]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1553 AAJ]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1554 AAR]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1569 JNR]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1560 PSV]]<br /> *[[CSC/ECE 517 Fall 2015/oss M1505 MSV]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1557 GXM]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1566 ARB]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1567 APT]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1574 BKS]]<br /> *[[CSC/ECE 517 Fall 2015/ossA1550RAN]]<br /> <br /> ==Final Project Design Document==<br /> *[[CSC/ECE 517 Fall 2015 E1577 MayYellowRoverJump]]<br /> *[[CSC/ECE 517 Fall 2015 E1586 AnonymousChatBetweenAuthorAndReviewer]]<br /> *[[CSC/ECE 517 Fall 2015 E1582 Create integration tests for the instructor interface using capybara and rspec]]<br /> *[[CSC/ECE 517 Fall 2015 E1576 Refactoring submitted content (hyperlinks and files)]]<br /> *[[CSC/ECE 517 Fall 2015 E1590 Integration testing for Team creation]]<br /> *[[CSC/ECE 517 Fall 2015 E1585 Use Ajax for Add Participants, Add TA ,Edit Questionnaires Screens]]</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=97939 2015-11-01T00:58:09Z

<p>Vpaul: /* Solutions to problems while setting up the repository */</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [https://github.com/gmeneze/expertiza Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [https://www.youtube.com/watch?v=yC_heDL6GSw Youtube video manual]<br /> <br /> ==Reviewer Instructions==<br /> ===Clone the reopsitory===<br /> Visit [https://github.com/gmeneze/expertiza Github repo] for the repository URL. Make sure you're logged in if you have commit access, because the URL will be different.<br /> <br /> git clone (repository URL)<br /> <br /> See https://help.github.com for help on setting up git, authenticating with SSH keys, and checking out a repository.<br /> <br /> ===Installing Gems (ruby dependencies)===<br /> In the expertiza directory:<br /> <br /> bundle install<br /> <br /> ===Set up databses===<br /> *Go to the expertiza directory.<br /> <br /> cd expertiza<br /> <br /> *Create the development and test databases.<br /> <br /> rake db:create:all<br /> <br /> *If available, import the database dump that you received in class to pre-populate your database. eg:<br /> <br /> mysql -u root expertiza_development &lt; expertiza-scrubbed.sql<br /> <br /> *Run the Expertiza database migrations. This should populate your database with the current tables of the schema.<br /> <br /> rake db:migrate<br /> <br /> ===Running the tests===<br /> *Go to the expertiza directory if you are not already there.<br /> <br /> *Run the test<br /> <br /> rspec spec/features/assignment_creation_spec.rb<br /> <br /> ==Solutions to problems while setting up the repository==<br /> ===rjb gem error===<br /> * To solve this, make sure that you have java installed on your system or else you could do that from [https://help.ubuntu.com/community/Java here].<br /> * Then set the JAVA_HOME environment variable by typing this on the terminal<br /> <br /> export JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64<br /> <br /> * Run bundle install again.<br /> <br /> ===pg gem error===<br /> * To solve this, we have to install PostgreSQL.<br /> * Then type in the following set of commands in the terminal<br /> <br /> sudo sh -c &quot;echo 'deb http://apt.postgresql.org/pub/repos/apt/ precise-pgdg main' &gt; /etc/apt/sources.list.d/pgdg.list&quot;<br /> wget --quiet -O - http://apt.postgresql.org/pub/repos/apt/ACCC4CF8.asc | sudo apt-key add -<br /> sudo apt-get update<br /> sudo apt-get install postgresql-common<br /> sudo apt-get install postgresql-9.3 libpq-dev<br /> <br /> *Run bundle install again<br /> <br /> ===Database related errors===<br /> * Here is the link of Expertiza scrubbed DB (https://drive.google.com/a/ncsu.edu/file/d/0B2vDvVjH76uESEkzSWpJRnhGbmc/view?usp=sharing)<br /> * Download the file, unzip it and dump to MySQL.<br /> * Then type<br /> <br /> rake db:migrate RAILS_ENV=development<br /> rake db:migrate RAILS_ENV=test<br /> <br /> ===Other errors===<br /> For any other kind of errors faced during setting up the repository, you can write to us at any of the following ids.<br /> <br /> * aslingwa@ncsu.edu<br /> * gmeneze@ncsu.edu<br /> * vpaul@ncsu.edu<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. One of the major reasons for selecting Capybara to write our tests was that it has an intuitive API which mimics the language an actual user would use and also we can run tests from fast headless mode to an actual browser with no changes to our tests.<br /> <br /> ==Flow of our test==<br /> [[File:test flow.png]]<br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=97935 2015-11-01T00:54:52Z

<p>Vpaul: /* Solutions to problems while setting up the repository */</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [https://github.com/gmeneze/expertiza Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [https://www.youtube.com/watch?v=yC_heDL6GSw Youtube video manual]<br /> <br /> ==Reviewer Instructions==<br /> ===Clone the reopsitory===<br /> Visit [https://github.com/gmeneze/expertiza Github repo] for the repository URL. Make sure you're logged in if you have commit access, because the URL will be different.<br /> <br /> git clone (repository URL)<br /> <br /> See https://help.github.com for help on setting up git, authenticating with SSH keys, and checking out a repository.<br /> <br /> ===Installing Gems (ruby dependencies)===<br /> In the expertiza directory:<br /> <br /> bundle install<br /> <br /> ===Set up databses===<br /> *Go to the expertiza directory.<br /> <br /> cd expertiza<br /> <br /> *Create the development and test databases.<br /> <br /> rake db:create:all<br /> <br /> *If available, import the database dump that you received in class to pre-populate your database. eg:<br /> <br /> mysql -u root expertiza_development &lt; expertiza-scrubbed.sql<br /> <br /> *Run the Expertiza database migrations. This should populate your database with the current tables of the schema.<br /> <br /> rake db:migrate<br /> <br /> ===Running the tests===<br /> *Go to the expertiza directory if you are not already there.<br /> <br /> *Run the test<br /> <br /> rspec spec/features/assignment_creation_spec.rb<br /> <br /> ==Solutions to problems while setting up the repository==<br /> ===rjb gem error===<br /> * To solve this, make sure that you have java installed on your system or else you could do that from [https://help.ubuntu.com/community/Java here].<br /> * Then set the JAVA_HOME environment variable by typing this on the terminal<br /> <br /> export JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64<br /> <br /> * Run bundle install again.<br /> <br /> ===pg gem error===<br /> * To solve this, we have to install PostgreSQL.<br /> * Then type in the following set of commands in the terminal<br /> <br /> sudo sh -c &quot;echo 'deb http://apt.postgresql.org/pub/repos/apt/ precise-pgdg main' &gt; /etc/apt/sources.list.d/pgdg.list&quot;<br /> wget --quiet -O - http://apt.postgresql.org/pub/repos/apt/ACCC4CF8.asc | sudo apt-key add -<br /> sudo apt-get update<br /> sudo apt-get install postgresql-common<br /> sudo apt-get install postgresql-9.3 libpq-dev<br /> <br /> *Run bundle install again<br /> <br /> ===Database related errors===<br /> * Here is the link of Expertiza scrubbed DB (https://drive.google.com/a/ncsu.edu/file/d/0B2vDvVjH76uESEkzSWpJRnhGbmc/view?usp=sharing)<br /> * Download the file, unzip it and dump to MySQL.<br /> * Then type<br /> <br /> rake db:migrate RAILS_ENV=development<br /> rake db:migrate RAILS_ENV=test<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. One of the major reasons for selecting Capybara to write our tests was that it has an intuitive API which mimics the language an actual user would use and also we can run tests from fast headless mode to an actual browser with no changes to our tests.<br /> <br /> ==Flow of our test==<br /> [[File:test flow.png]]<br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=97868 2015-11-01T00:01:25Z

<p>Vpaul: /* Solutions to problems while setting up the repository */</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [https://github.com/gmeneze/expertiza Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [https://www.youtube.com/watch?v=yC_heDL6GSw Youtube video manual]<br /> <br /> ==Reviewer Instructions==<br /> ===Clone the reopsitory===<br /> Visit [https://github.com/gmeneze/expertiza Github repo] for the repository URL. Make sure you're logged in if you have commit access, because the URL will be different.<br /> <br /> git clone (repository URL)<br /> <br /> See https://help.github.com for help on setting up git, authenticating with SSH keys, and checking out a repository.<br /> <br /> ===Installing Gems (ruby dependencies)===<br /> In the expertiza directory:<br /> <br /> bundle install<br /> <br /> ===Set up databses===<br /> *Go to the expertiza directory.<br /> <br /> cd expertiza<br /> <br /> *Create the development and test databases.<br /> <br /> rake db:create:all<br /> <br /> *If available, import the database dump that you received in class to pre-populate your database. eg:<br /> <br /> mysql -u root expertiza_development &lt; expertiza-scrubbed.sql<br /> <br /> *Run the Expertiza database migrations. This should populate your database with the current tables of the schema.<br /> <br /> rake db:migrate<br /> <br /> ===Running the tests===<br /> *Go to the expertiza directory if you are not already there.<br /> <br /> *Run the test<br /> <br /> rspec spec/features/assignment_creation_spec.rb<br /> <br /> ==Solutions to problems while setting up the repository==<br /> ===rjb gem error===<br /> * To solve this, make sure that you have java installed on your system or else you could do that from [https://help.ubuntu.com/community/Java here].<br /> * Then set the JAVA_HOME environment variable by typing this on the terminal<br /> <br /> export JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64<br /> <br /> * Run bundle install again.<br /> <br /> ===pg gem error===<br /> * To solve this, we have to install PostgreSQL.<br /> * Then type in the following set of commands in the terminal<br /> <br /> sudo sh -c &quot;echo 'deb http://apt.postgresql.org/pub/repos/apt/ precise-pgdg main' &gt; /etc/apt/sources.list.d/pgdg.list&quot;<br /> wget --quiet -O - http://apt.postgresql.org/pub/repos/apt/ACCC4CF8.asc | sudo apt-key add -<br /> sudo apt-get update<br /> sudo apt-get install postgresql-common<br /> sudo apt-get install postgresql-9.3 libpq-dev<br /> <br /> *Run bundle install again<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. One of the major reasons for selecting Capybara to write our tests was that it has an intuitive API which mimics the language an actual user would use and also we can run tests from fast headless mode to an actual browser with no changes to our tests.<br /> <br /> ==Flow of our test==<br /> [[File:test flow.png]]<br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=97853 2015-10-31T23:38:39Z

<p>Vpaul: /* rjb error */</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [https://github.com/gmeneze/expertiza Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [https://www.youtube.com/watch?v=yC_heDL6GSw Youtube video manual]<br /> <br /> ==Reviewer Instructions==<br /> ===Clone the reopsitory===<br /> Visit [https://github.com/gmeneze/expertiza Github repo] for the repository URL. Make sure you're logged in if you have commit access, because the URL will be different.<br /> <br /> git clone (repository URL)<br /> <br /> See https://help.github.com for help on setting up git, authenticating with SSH keys, and checking out a repository.<br /> <br /> ===Installing Gems (ruby dependencies)===<br /> In the expertiza directory:<br /> <br /> bundle install<br /> <br /> ===Set up databses===<br /> *Go to the expertiza directory.<br /> <br /> cd expertiza<br /> <br /> *Create the development and test databases.<br /> <br /> rake db:create:all<br /> <br /> *If available, import the database dump that you received in class to pre-populate your database. eg:<br /> <br /> mysql -u root expertiza_development &lt; expertiza-scrubbed.sql<br /> <br /> *Run the Expertiza database migrations. This should populate your database with the current tables of the schema.<br /> <br /> rake db:migrate<br /> <br /> ===Running the tests===<br /> *Go to the expertiza directory if you are not already there.<br /> <br /> *Run the test<br /> <br /> rspec spec/features/assignment_creation_spec.rb<br /> <br /> ==Solutions to problems while setting up the repository==<br /> ===rjb error===<br /> * To solve this, make sure that you have java installed on your system or else you could do that from [https://help.ubuntu.com/community/Java here].<br /> * Then set the JAVA_HOME environment variable by typing this on the terminal<br /> <br /> export JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. One of the major reasons for selecting Capybara to write our tests was that it has an intuitive API which mimics the language an actual user would use and also we can run tests from fast headless mode to an actual browser with no changes to our tests.<br /> <br /> ==Flow of our test==<br /> [[File:test flow.png]]<br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=97852 2015-10-31T23:36:50Z

<p>Vpaul: </p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [https://github.com/gmeneze/expertiza Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [https://www.youtube.com/watch?v=yC_heDL6GSw Youtube video manual]<br /> <br /> ==Reviewer Instructions==<br /> ===Clone the reopsitory===<br /> Visit [https://github.com/gmeneze/expertiza Github repo] for the repository URL. Make sure you're logged in if you have commit access, because the URL will be different.<br /> <br /> git clone (repository URL)<br /> <br /> See https://help.github.com for help on setting up git, authenticating with SSH keys, and checking out a repository.<br /> <br /> ===Installing Gems (ruby dependencies)===<br /> In the expertiza directory:<br /> <br /> bundle install<br /> <br /> ===Set up databses===<br /> *Go to the expertiza directory.<br /> <br /> cd expertiza<br /> <br /> *Create the development and test databases.<br /> <br /> rake db:create:all<br /> <br /> *If available, import the database dump that you received in class to pre-populate your database. eg:<br /> <br /> mysql -u root expertiza_development &lt; expertiza-scrubbed.sql<br /> <br /> *Run the Expertiza database migrations. This should populate your database with the current tables of the schema.<br /> <br /> rake db:migrate<br /> <br /> ===Running the tests===<br /> *Go to the expertiza directory if you are not already there.<br /> <br /> *Run the test<br /> <br /> rspec spec/features/assignment_creation_spec.rb<br /> <br /> ==Solutions to problems while setting up the repository==<br /> ===rjb error===<br /> * To solve this, make sure that you have java installed on your system or else you could do that from [http://apt.ubuntu.com/p/openjdk-7-jdk here].<br /> * Then set the JAVA_HOME environment variable by typing this on the terminal<br /> <br /> export JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64<br /> <br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. One of the major reasons for selecting Capybara to write our tests was that it has an intuitive API which mimics the language an actual user would use and also we can run tests from fast headless mode to an actual browser with no changes to our tests.<br /> <br /> ==Flow of our test==<br /> [[File:test flow.png]]<br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=97725 2015-10-31T21:50:09Z

<p>Vpaul: /* Reviewer Instructions */</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [https://github.com/gmeneze/expertiza Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [https://www.youtube.com/watch?v=yC_heDL6GSw Youtube video manual]<br /> <br /> ==Reviewer Instructions==<br /> ===Clone the reopsitory===<br /> Visit [https://github.com/gmeneze/expertiza Github repo] for the repository URL. Make sure you're logged in if you have commit access, because the URL will be different.<br /> <br /> git clone (repository URL)<br /> <br /> See https://help.github.com for help on setting up git, authenticating with SSH keys, and checking out a repository.<br /> <br /> ===Installing Gems (ruby dependencies)===<br /> In the expertiza directory:<br /> <br /> bundle install<br /> <br /> ===Set up databses===<br /> *Go to the expertiza directory.<br /> <br /> cd expertiza<br /> <br /> *Create the development and test databases.<br /> <br /> rake db:create:all<br /> <br /> *If available, import the database dump that you received in class to pre-populate your database. eg:<br /> <br /> mysql -u root expertiza_development &lt; expertiza-scrubbed.sql<br /> <br /> *Run the Expertiza database migrations. This should populate your database with the current tables of the schema.<br /> <br /> rake db:migrate<br /> <br /> ===Running the tests===<br /> *Go to the expertiza directory if you are not already there.<br /> <br /> *Run the test<br /> <br /> rspec spec/features/assignment_creation_spec.rb<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. One of the major reasons for selecting Capybara to write our tests was that it has an intuitive API which mimics the language an actual user would use and also we can run tests from fast headless mode to an actual browser with no changes to our tests.<br /> <br /> ==Flow of our test==<br /> [[File:test flow.png]]<br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=97721 2015-10-31T21:47:10Z

<p>Vpaul: </p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [https://github.com/gmeneze/expertiza Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [https://www.youtube.com/watch?v=yC_heDL6GSw Youtube video manual]<br /> <br /> ==Reviewer Instructions==<br /> ===Clone the reopsitory===<br /> Visit [https://github.com/expertiza/expertiza Github repo] for the repository URL. Make sure you're logged in if you have commit access, because the URL will be different.<br /> <br /> git clone (repository URL)<br /> <br /> See https://help.github.com for help on setting up git, authenticating with SSH keys, and checking out a repository.<br /> <br /> ===Installing Gems (ruby dependencies)===<br /> In the expertiza directory:<br /> <br /> bundle install<br /> <br /> ===Set up databses===<br /> *Go to the expertiza directory.<br /> <br /> cd expertiza<br /> <br /> *Create the development and test databases.<br /> <br /> rake db:create:all<br /> <br /> *If available, import the database dump that you received in class to pre-populate your database. eg:<br /> <br /> mysql -u root expertiza_development &lt; expertiza-scrubbed.sql<br /> <br /> *Run the Expertiza database migrations. This should populate your database with the current tables of the schema.<br /> <br /> rake db:migrate<br /> <br /> ===Running the tests===<br /> *Go to the expertiza directory if you are not already there.<br /> <br /> *Run the test<br /> <br /> rspec spec/features/assignment_creation_spec.rb<br /> <br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. One of the major reasons for selecting Capybara to write our tests was that it has an intuitive API which mimics the language an actual user would use and also we can run tests from fast headless mode to an actual browser with no changes to our tests.<br /> <br /> ==Flow of our test==<br /> [[File:test flow.png]]<br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=File:Test_flow.png&diff=97351 2015-10-30T18:20:31Z

<p>Vpaul: This represents the flow of our tests.</p> <hr /> <div>This represents the flow of our tests.</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=97350 2015-10-30T18:19:19Z

<p>Vpaul: </p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Reviewer Instructions==<br /> ===Clone the reopsitory===<br /> Visit [https://github.com/expertiza/expertiza Github repo] for the repository URL. Make sure you're logged in if you have commit access, because the URL will be different.<br /> <br /> git clone (repository URL)<br /> <br /> See https://help.github.com for help on setting up git, authenticating with SSH keys, and checking out a repository.<br /> <br /> ===Installing Gems (ruby dependencies)===<br /> In the expertiza directory:<br /> <br /> bundle install<br /> <br /> ===Set up databses===<br /> *Go to the expertiza directory.<br /> <br /> cd expertiza<br /> <br /> *Create the development and test databases.<br /> <br /> rake db:create:all<br /> <br /> *If available, import the database dump that you received in class to pre-populate your database. eg:<br /> <br /> mysql -u root expertiza_development &lt; expertiza-scrubbed.sql<br /> <br /> *Run the Expertiza database migrations. This should populate your database with the current tables of the schema.<br /> <br /> rake db:migrate<br /> <br /> ===Running the tests===<br /> *Go to the expertiza directory if you are not already there.<br /> <br /> *Run the test<br /> <br /> rspec spec/features/assignment_creation_spec.rb<br /> <br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. One of the major reasons for selecting Capybara to write our tests was that it has an intuitive API which mimics the language an actual user would use and also we can run tests from fast headless mode to an actual browser with no changes to our tests.<br /> <br /> ==Flow of our test==<br /> [[File:test flow.png]]<br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=97345 2015-10-30T17:49:25Z

<p>Vpaul: /* Classes Involved */</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Reviewer Instructions==<br /> ===Clone the reopsitory===<br /> Visit [https://github.com/expertiza/expertiza Github repo] for the repository URL. Make sure you're logged in if you have commit access, because the URL will be different.<br /> <br /> git clone (repository URL)<br /> <br /> See https://help.github.com for help on setting up git, authenticating with SSH keys, and checking out a repository.<br /> <br /> ===Installing Gems (ruby dependencies)===<br /> In the expertiza directory:<br /> <br /> bundle install<br /> <br /> ===Set up databses===<br /> *Go to the expertiza directory.<br /> <br /> cd expertiza<br /> <br /> *Create the development and test databases.<br /> <br /> rake db:create:all<br /> <br /> *If available, import the database dump that you received in class to pre-populate your database. eg:<br /> <br /> mysql -u root expertiza_development &lt; expertiza-scrubbed.sql<br /> <br /> *Run the Expertiza database migrations. This should populate your database with the current tables of the schema.<br /> <br /> rake db:migrate<br /> <br /> ===Running the tests===<br /> *Go to the expertiza directory if you are not already there.<br /> <br /> *Run the test<br /> <br /> rspec spec/features/assignment_creation_spec.rb<br /> <br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. One of the major reasons for selecting Capybara to write our tests was that it has an intuitive API which mimics the language an actual user would use and also we can run tests from fast headless mode to an actual browser with no changes to our tests.<br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=97343 2015-10-30T17:16:33Z

<p>Vpaul: /* Code */</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Reviewer Instructions==<br /> ===Clone the reopsitory===<br /> Visit [https://github.com/expertiza/expertiza Github repo] for the repository URL. Make sure you're logged in if you have commit access, because the URL will be different.<br /> <br /> git clone (repository URL)<br /> <br /> See https://help.github.com for help on setting up git, authenticating with SSH keys, and checking out a repository.<br /> <br /> ===Installing Gems (ruby dependencies)===<br /> In the expertiza directory:<br /> <br /> bundle install<br /> <br /> ===Set up databses===<br /> *Go to the expertiza directory.<br /> <br /> cd expertiza<br /> <br /> *Create the development and test databases.<br /> <br /> rake db:create:all<br /> <br /> *If available, import the database dump that you received in class to pre-populate your database. eg:<br /> <br /> mysql -u root expertiza_development &lt; expertiza-scrubbed.sql<br /> <br /> *Run the Expertiza database migrations. This should populate your database with the current tables of the schema.<br /> <br /> rake db:migrate<br /> <br /> ===Running the tests===<br /> *Go to the expertiza directory if you are not already there.<br /> <br /> *Run the test<br /> <br /> rspec spec/features/assignment_creation_spec.rb<br /> <br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=97342 2015-10-30T17:15:33Z

<p>Vpaul: /* assignment_creation.rb */</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Reviewer Instructions==<br /> ===Clone the reopsitory===<br /> Visit [https://github.com/expertiza/expertiza Github repo] for the repository URL. Make sure you're logged in if you have commit access, because the URL will be different.<br /> <br /> git clone (repository URL)<br /> <br /> See https://help.github.com for help on setting up git, authenticating with SSH keys, and checking out a repository.<br /> <br /> ===Installing Gems (ruby dependencies)===<br /> In the expertiza directory:<br /> <br /> bundle install<br /> <br /> ===Set up databses===<br /> *Go to the expertiza directory.<br /> <br /> cd expertiza<br /> <br /> *Create the development and test databases.<br /> <br /> rake db:create:all<br /> <br /> *If available, import the database dump that you received in class to pre-populate your database. eg:<br /> <br /> mysql -u root expertiza_development &lt; expertiza-scrubbed.sql<br /> <br /> *Run the Expertiza database migrations. This should populate your database with the current tables of the schema.<br /> <br /> rake db:migrate<br /> <br /> ===Running the tests===<br /> *Go to the expertiza directory if you are not already there.<br /> <br /> *Run the test<br /> <br /> rspec spec/features/assignment_creation_spec.rb<br /> <br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> ===spec_helper.rb===<br /> # This file was generated by the `rails generate rspec:install` command. Conventionally, all<br /> # specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.<br /> # The generated `.rspec` file contains `--require spec_helper` which will cause<br /> # this file to always be loaded, without a need to explicitly require it in any<br /> # files.<br /> #<br /> # Given that it is always loaded, you are encouraged to keep this file as<br /> # light-weight as possible. Requiring heavyweight dependencies from this file<br /> # will add to the boot time of your test suite on EVERY test run, even for an<br /> # individual file that may not need all of that loaded. Instead, consider making<br /> # a separate helper file that requires the additional dependencies and performs<br /> # the additional setup, and require it from the spec files that actually need<br /> # it.<br /> #<br /> # The `.rspec` file also contains a few flags that are not defaults but that<br /> # users commonly want.<br /> #<br /> # See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration<br /> RSpec.configure do |config|<br /> # rspec-expectations config goes here. You can use an alternate<br /> # assertion/expectation library such as wrong or the stdlib/minitest<br /> # assertions if you prefer.<br /> #<br /> config.expect_with :rspec do |expectations|<br /> # This option will default to `true` in RSpec 4. It makes the `description`<br /> # and `failure_message` of custom matchers include text for helper methods<br /> # defined using `chain`, e.g.:<br /> # be_bigger_than(2).and_smaller_than(4).description<br /> # # =&gt; &quot;be bigger than 2 and smaller than 4&quot;<br /> # ...rather than:<br /> # # =&gt; &quot;be bigger than 2&quot;<br /> expectations.include_chain_clauses_in_custom_matcher_descriptions = true<br /> end<br /> #<br /> # rspec-mocks config goes here. You can use an alternate test double<br /> # library (such as bogus or mocha) by changing the `mock_with` option here.<br /> config.mock_with :rspec do |mocks|<br /> # Prevents you from mocking or stubbing a method that does not exist on<br /> # a real object. This is generally recommended, and will default to<br /> # `true` in RSpec 4.<br /> mocks.verify_partial_doubles = true<br /> end<br /> #<br /> # The settings below are suggested to provide a good initial experience<br /> # with RSpec, but feel free to customize to your heart's content.<br /> =begin<br /> # These two settings work together to allow you to limit a spec run<br /> # to individual examples or groups you care about by tagging them with<br /> # `:focus` metadata. When nothing is tagged with `:focus`, all examples<br /> # get run.<br /> config.filter_run :focus<br /> config.run_all_when_everything_filtered = true<br /> # Allows RSpec to persist some state between runs in order to support<br /> # the `--only-failures` and `--next-failure` CLI options. We recommend<br /> # you configure your source control system to ignore this file.<br /> config.example_status_persistence_file_path = &quot;spec/examples.txt&quot;<br /> # Limits the available syntax to the non-monkey patched syntax that is<br /> # recommended. For more details, see:<br /> # - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax<br /> # - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/<br /> # - http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new__config_option_to_disable_rspeccore_monkey_patching<br /> config.disable_monkey_patching!<br /> # Many RSpec users commonly either run the entire suite or an individual<br /> # file, and it's useful to allow more verbose output when running an<br /> # individual spec file.<br /> if config.files_to_run.one?<br /> # Use the documentation formatter for detailed output,<br /> # unless a formatter has already been configured<br /> # (e.g. via a command-line flag).<br /> config.default_formatter = 'doc'<br /> end<br /> # Print the 10 slowest examples and example groups at the<br /> # end of the spec run, to help surface which specs are running<br /> # particularly slow.<br /> config.profile_examples = 10<br /> # Run specs in random order to surface order dependencies. If you find an<br /> # order dependency and want to debug it, you can fix the order by providing<br /> # the seed, which is printed after each run.<br /> # --seed 1234<br /> config.order = :random<br /> # Seed global randomization in this process using the `--seed` CLI option.<br /> # Setting this allows you to use `--seed` to deterministically reproduce<br /> # test failures related to randomization by passing the same `--seed` value<br /> # as the one that triggered the failure.<br /> Kernel.srand config.seed<br /> =end<br /> end<br /> <br /> ===rails_helper.rb===<br /> <br /> # This file is copied to spec/ when you run 'rails generate rspec:install'<br /> ENV['RAILS_ENV'] ||= 'test'<br /> require File.expand_path('../../config/environment', __FILE__)<br /> # Prevent database truncation if the environment is production<br /> abort(&quot;The Rails environment is running in production mode!&quot;) if Rails.env.production?<br /> require 'spec_helper'<br /> require 'rspec/rails'<br /> # Add additional requires below this line. Rails is not loaded until this point!<br /> #<br /> # Requires supporting ruby files with custom matchers and macros, etc, in<br /> # spec/support/ and its subdirectories. Files matching `spec/**/*_spec.rb` are<br /> # run as spec files by default. This means that files in spec/support that end<br /> # in _spec.rb will both be required and run as specs, causing the specs to be<br /> # run twice. It is recommended that you do not name files matching this glob to<br /> # end with _spec.rb. You can configure this pattern with the --pattern<br /> # option on the command line or in ~/.rspec, .rspec or `.rspec-local`.<br /> #<br /> # The following line is provided for convenience purposes. It has the downside<br /> # of increasing the boot-up time by auto-requiring all files in the support<br /> # directory. Alternatively, in the individual `*_spec.rb` files, manually<br /> # require only the support files necessary. <br /> #<br /> # Dir[Rails.root.join('spec/support/**/*.rb')].each { |f| require f }<br /> #<br /> # Checks for pending migrations before tests are run.<br /> # If you are not using ActiveRecord, you can remove this line.<br /> ActiveRecord::Migration.maintain_test_schema!<br /> RSpec.configure do |config|<br /> # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures<br /> config.fixture_path = &quot;#{::Rails.root}/spec/fixtures&quot;<br /> config.include FactoryGirl::Syntax::Methods<br /> #<br /> # If you're not using ActiveRecord, or you'd prefer not to run each of your<br /> # examples within a transaction, remove the following line or assign false<br /> # instead of true.<br /> # config.use_transactional_fixtures = true<br /> # config.before(:suite) do<br /> # DatabaseCleaner.clean_with(:truncation,:only =&gt; ['users'])<br /> # end<br /> # config.before(:each) do<br /> # DatabaseCleaner.strategy = :transaction<br /> # end<br /> # config.before(:each, :js =&gt; true) do<br /> # DatabaseCleaner.strategy = :truncation<br /> # end<br /> # config.before(:each) do<br /> # DatabaseCleaner.start<br /> # end<br /> #<br /> # RSpec Rails can automatically mix in different behaviours to your tests<br /> # based on their file location, for example enabling you to call `get` and<br /> # `post` in specs under `spec/controllers`.<br /> #<br /> # You can disable this behaviour by removing the line below, and instead<br /> # explicitly tag your specs with their type, e.g.:<br /> #<br /> # RSpec.describe UsersController, :type =&gt; :controller do<br /> # # ...<br /> # end<br /> #<br /> # The different available types are documented in the features, such as in<br /> # https://relishapp.com/rspec/rspec-rails/docs<br /> config.infer_spec_type_from_file_location! <br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=97335 2015-10-30T15:41:02Z

<p>Vpaul: </p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Reviewer Instructions==<br /> ===Clone the reopsitory===<br /> Visit [https://github.com/expertiza/expertiza Github repo] for the repository URL. Make sure you're logged in if you have commit access, because the URL will be different.<br /> <br /> git clone (repository URL)<br /> <br /> See https://help.github.com for help on setting up git, authenticating with SSH keys, and checking out a repository.<br /> <br /> ===Installing Gems (ruby dependencies)===<br /> In the expertiza directory:<br /> <br /> bundle install<br /> <br /> ===Set up databses===<br /> *Go to the expertiza directory.<br /> <br /> cd expertiza<br /> <br /> *Create the development and test databases.<br /> <br /> rake db:create:all<br /> <br /> *If available, import the database dump that you received in class to pre-populate your database. eg:<br /> <br /> mysql -u root expertiza_development &lt; expertiza-scrubbed.sql<br /> <br /> *Run the Expertiza database migrations. This should populate your database with the current tables of the schema.<br /> <br /> rake db:migrate<br /> <br /> ===Running the tests===<br /> *Go to the expertiza directory if you are not already there.<br /> <br /> *Run the test<br /> <br /> rspec spec/features/assignment_creation_spec.rb<br /> <br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> scenario &quot;Create Assignment with Wiki assignment?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_wiki_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Reviews visible to all other reviewers?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_reviews_visible_to_all')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with negative scenario&quot;, :skip_before, :js =&gt; true do<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> click_on('Create')<br /> expect(page).to have_content(&quot;New Assignment&quot;)<br /> end <br /> end <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> ===spec_helper.rb===<br /> # This file was generated by the `rails generate rspec:install` command. Conventionally, all<br /> # specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.<br /> # The generated `.rspec` file contains `--require spec_helper` which will cause<br /> # this file to always be loaded, without a need to explicitly require it in any<br /> # files.<br /> #<br /> # Given that it is always loaded, you are encouraged to keep this file as<br /> # light-weight as possible. Requiring heavyweight dependencies from this file<br /> # will add to the boot time of your test suite on EVERY test run, even for an<br /> # individual file that may not need all of that loaded. Instead, consider making<br /> # a separate helper file that requires the additional dependencies and performs<br /> # the additional setup, and require it from the spec files that actually need<br /> # it.<br /> #<br /> # The `.rspec` file also contains a few flags that are not defaults but that<br /> # users commonly want.<br /> #<br /> # See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration<br /> RSpec.configure do |config|<br /> # rspec-expectations config goes here. You can use an alternate<br /> # assertion/expectation library such as wrong or the stdlib/minitest<br /> # assertions if you prefer.<br /> #<br /> config.expect_with :rspec do |expectations|<br /> # This option will default to `true` in RSpec 4. It makes the `description`<br /> # and `failure_message` of custom matchers include text for helper methods<br /> # defined using `chain`, e.g.:<br /> # be_bigger_than(2).and_smaller_than(4).description<br /> # # =&gt; &quot;be bigger than 2 and smaller than 4&quot;<br /> # ...rather than:<br /> # # =&gt; &quot;be bigger than 2&quot;<br /> expectations.include_chain_clauses_in_custom_matcher_descriptions = true<br /> end<br /> #<br /> # rspec-mocks config goes here. You can use an alternate test double<br /> # library (such as bogus or mocha) by changing the `mock_with` option here.<br /> config.mock_with :rspec do |mocks|<br /> # Prevents you from mocking or stubbing a method that does not exist on<br /> # a real object. This is generally recommended, and will default to<br /> # `true` in RSpec 4.<br /> mocks.verify_partial_doubles = true<br /> end<br /> #<br /> # The settings below are suggested to provide a good initial experience<br /> # with RSpec, but feel free to customize to your heart's content.<br /> =begin<br /> # These two settings work together to allow you to limit a spec run<br /> # to individual examples or groups you care about by tagging them with<br /> # `:focus` metadata. When nothing is tagged with `:focus`, all examples<br /> # get run.<br /> config.filter_run :focus<br /> config.run_all_when_everything_filtered = true<br /> # Allows RSpec to persist some state between runs in order to support<br /> # the `--only-failures` and `--next-failure` CLI options. We recommend<br /> # you configure your source control system to ignore this file.<br /> config.example_status_persistence_file_path = &quot;spec/examples.txt&quot;<br /> # Limits the available syntax to the non-monkey patched syntax that is<br /> # recommended. For more details, see:<br /> # - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax<br /> # - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/<br /> # - http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new__config_option_to_disable_rspeccore_monkey_patching<br /> config.disable_monkey_patching!<br /> # Many RSpec users commonly either run the entire suite or an individual<br /> # file, and it's useful to allow more verbose output when running an<br /> # individual spec file.<br /> if config.files_to_run.one?<br /> # Use the documentation formatter for detailed output,<br /> # unless a formatter has already been configured<br /> # (e.g. via a command-line flag).<br /> config.default_formatter = 'doc'<br /> end<br /> # Print the 10 slowest examples and example groups at the<br /> # end of the spec run, to help surface which specs are running<br /> # particularly slow.<br /> config.profile_examples = 10<br /> # Run specs in random order to surface order dependencies. If you find an<br /> # order dependency and want to debug it, you can fix the order by providing<br /> # the seed, which is printed after each run.<br /> # --seed 1234<br /> config.order = :random<br /> # Seed global randomization in this process using the `--seed` CLI option.<br /> # Setting this allows you to use `--seed` to deterministically reproduce<br /> # test failures related to randomization by passing the same `--seed` value<br /> # as the one that triggered the failure.<br /> Kernel.srand config.seed<br /> =end<br /> end<br /> <br /> ===rails_helper.rb===<br /> <br /> # This file is copied to spec/ when you run 'rails generate rspec:install'<br /> ENV['RAILS_ENV'] ||= 'test'<br /> require File.expand_path('../../config/environment', __FILE__)<br /> # Prevent database truncation if the environment is production<br /> abort(&quot;The Rails environment is running in production mode!&quot;) if Rails.env.production?<br /> require 'spec_helper'<br /> require 'rspec/rails'<br /> # Add additional requires below this line. Rails is not loaded until this point!<br /> #<br /> # Requires supporting ruby files with custom matchers and macros, etc, in<br /> # spec/support/ and its subdirectories. Files matching `spec/**/*_spec.rb` are<br /> # run as spec files by default. This means that files in spec/support that end<br /> # in _spec.rb will both be required and run as specs, causing the specs to be<br /> # run twice. It is recommended that you do not name files matching this glob to<br /> # end with _spec.rb. You can configure this pattern with the --pattern<br /> # option on the command line or in ~/.rspec, .rspec or `.rspec-local`.<br /> #<br /> # The following line is provided for convenience purposes. It has the downside<br /> # of increasing the boot-up time by auto-requiring all files in the support<br /> # directory. Alternatively, in the individual `*_spec.rb` files, manually<br /> # require only the support files necessary. <br /> #<br /> # Dir[Rails.root.join('spec/support/**/*.rb')].each { |f| require f }<br /> #<br /> # Checks for pending migrations before tests are run.<br /> # If you are not using ActiveRecord, you can remove this line.<br /> ActiveRecord::Migration.maintain_test_schema!<br /> RSpec.configure do |config|<br /> # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures<br /> config.fixture_path = &quot;#{::Rails.root}/spec/fixtures&quot;<br /> config.include FactoryGirl::Syntax::Methods<br /> #<br /> # If you're not using ActiveRecord, or you'd prefer not to run each of your<br /> # examples within a transaction, remove the following line or assign false<br /> # instead of true.<br /> # config.use_transactional_fixtures = true<br /> # config.before(:suite) do<br /> # DatabaseCleaner.clean_with(:truncation,:only =&gt; ['users'])<br /> # end<br /> # config.before(:each) do<br /> # DatabaseCleaner.strategy = :transaction<br /> # end<br /> # config.before(:each, :js =&gt; true) do<br /> # DatabaseCleaner.strategy = :truncation<br /> # end<br /> # config.before(:each) do<br /> # DatabaseCleaner.start<br /> # end<br /> #<br /> # RSpec Rails can automatically mix in different behaviours to your tests<br /> # based on their file location, for example enabling you to call `get` and<br /> # `post` in specs under `spec/controllers`.<br /> #<br /> # You can disable this behaviour by removing the line below, and instead<br /> # explicitly tag your specs with their type, e.g.:<br /> #<br /> # RSpec.describe UsersController, :type =&gt; :controller do<br /> # # ...<br /> # end<br /> #<br /> # The different available types are documented in the features, such as in<br /> # https://relishapp.com/rspec/rspec-rails/docs<br /> config.infer_spec_type_from_file_location! <br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=97333 2015-10-30T15:39:53Z

<p>Vpaul: </p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Reviewer Instructions==<br /> ===Clone the reopsitory===<br /> Visit [https://github.com/expertiza/expertiza Github repo] for the repository URL. Make sure you're logged in if you have commit access, because the URL will be different.<br /> <br /> git clone (repository URL)<br /> <br /> See https://help.github.com for help on setting up git, authenticating with SSH keys, and checking out a repository.<br /> <br /> ===Installing Gems (ruby dependencies)===<br /> In the expertiza directory:<br /> <br /> bundle install<br /> <br /> ===Set up databses===<br /> #Go to the expertiza directory.<br /> <br /> cd expertiza<br /> <br /> #Create the development and test databases.<br /> <br /> rake db:create:all<br /> <br /> #If available, import the database dump that you received in class to pre-populate your database. eg:<br /> <br /> mysql -u root expertiza_development &lt; expertiza-scrubbed.sql<br /> <br /> #Run the Expertiza database migrations. This should populate your database with the current tables of the schema.<br /> <br /> rake db:migrate<br /> <br /> ===Running the tests===<br /> #Go to the expertiza directory if you are not already there.<br /> <br /> #Run the test<br /> <br /> rspec spec/features/assignment_creation_spec.rb<br /> <br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> scenario &quot;Create Assignment with Wiki assignment?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_wiki_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Reviews visible to all other reviewers?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_reviews_visible_to_all')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with negative scenario&quot;, :skip_before, :js =&gt; true do<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> click_on('Create')<br /> expect(page).to have_content(&quot;New Assignment&quot;)<br /> end <br /> end <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> ===spec_helper.rb===<br /> # This file was generated by the `rails generate rspec:install` command. Conventionally, all<br /> # specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.<br /> # The generated `.rspec` file contains `--require spec_helper` which will cause<br /> # this file to always be loaded, without a need to explicitly require it in any<br /> # files.<br /> #<br /> # Given that it is always loaded, you are encouraged to keep this file as<br /> # light-weight as possible. Requiring heavyweight dependencies from this file<br /> # will add to the boot time of your test suite on EVERY test run, even for an<br /> # individual file that may not need all of that loaded. Instead, consider making<br /> # a separate helper file that requires the additional dependencies and performs<br /> # the additional setup, and require it from the spec files that actually need<br /> # it.<br /> #<br /> # The `.rspec` file also contains a few flags that are not defaults but that<br /> # users commonly want.<br /> #<br /> # See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration<br /> RSpec.configure do |config|<br /> # rspec-expectations config goes here. You can use an alternate<br /> # assertion/expectation library such as wrong or the stdlib/minitest<br /> # assertions if you prefer.<br /> #<br /> config.expect_with :rspec do |expectations|<br /> # This option will default to `true` in RSpec 4. It makes the `description`<br /> # and `failure_message` of custom matchers include text for helper methods<br /> # defined using `chain`, e.g.:<br /> # be_bigger_than(2).and_smaller_than(4).description<br /> # # =&gt; &quot;be bigger than 2 and smaller than 4&quot;<br /> # ...rather than:<br /> # # =&gt; &quot;be bigger than 2&quot;<br /> expectations.include_chain_clauses_in_custom_matcher_descriptions = true<br /> end<br /> #<br /> # rspec-mocks config goes here. You can use an alternate test double<br /> # library (such as bogus or mocha) by changing the `mock_with` option here.<br /> config.mock_with :rspec do |mocks|<br /> # Prevents you from mocking or stubbing a method that does not exist on<br /> # a real object. This is generally recommended, and will default to<br /> # `true` in RSpec 4.<br /> mocks.verify_partial_doubles = true<br /> end<br /> #<br /> # The settings below are suggested to provide a good initial experience<br /> # with RSpec, but feel free to customize to your heart's content.<br /> =begin<br /> # These two settings work together to allow you to limit a spec run<br /> # to individual examples or groups you care about by tagging them with<br /> # `:focus` metadata. When nothing is tagged with `:focus`, all examples<br /> # get run.<br /> config.filter_run :focus<br /> config.run_all_when_everything_filtered = true<br /> # Allows RSpec to persist some state between runs in order to support<br /> # the `--only-failures` and `--next-failure` CLI options. We recommend<br /> # you configure your source control system to ignore this file.<br /> config.example_status_persistence_file_path = &quot;spec/examples.txt&quot;<br /> # Limits the available syntax to the non-monkey patched syntax that is<br /> # recommended. For more details, see:<br /> # - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax<br /> # - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/<br /> # - http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new__config_option_to_disable_rspeccore_monkey_patching<br /> config.disable_monkey_patching!<br /> # Many RSpec users commonly either run the entire suite or an individual<br /> # file, and it's useful to allow more verbose output when running an<br /> # individual spec file.<br /> if config.files_to_run.one?<br /> # Use the documentation formatter for detailed output,<br /> # unless a formatter has already been configured<br /> # (e.g. via a command-line flag).<br /> config.default_formatter = 'doc'<br /> end<br /> # Print the 10 slowest examples and example groups at the<br /> # end of the spec run, to help surface which specs are running<br /> # particularly slow.<br /> config.profile_examples = 10<br /> # Run specs in random order to surface order dependencies. If you find an<br /> # order dependency and want to debug it, you can fix the order by providing<br /> # the seed, which is printed after each run.<br /> # --seed 1234<br /> config.order = :random<br /> # Seed global randomization in this process using the `--seed` CLI option.<br /> # Setting this allows you to use `--seed` to deterministically reproduce<br /> # test failures related to randomization by passing the same `--seed` value<br /> # as the one that triggered the failure.<br /> Kernel.srand config.seed<br /> =end<br /> end<br /> <br /> ===rails_helper.rb===<br /> <br /> # This file is copied to spec/ when you run 'rails generate rspec:install'<br /> ENV['RAILS_ENV'] ||= 'test'<br /> require File.expand_path('../../config/environment', __FILE__)<br /> # Prevent database truncation if the environment is production<br /> abort(&quot;The Rails environment is running in production mode!&quot;) if Rails.env.production?<br /> require 'spec_helper'<br /> require 'rspec/rails'<br /> # Add additional requires below this line. Rails is not loaded until this point!<br /> #<br /> # Requires supporting ruby files with custom matchers and macros, etc, in<br /> # spec/support/ and its subdirectories. Files matching `spec/**/*_spec.rb` are<br /> # run as spec files by default. This means that files in spec/support that end<br /> # in _spec.rb will both be required and run as specs, causing the specs to be<br /> # run twice. It is recommended that you do not name files matching this glob to<br /> # end with _spec.rb. You can configure this pattern with the --pattern<br /> # option on the command line or in ~/.rspec, .rspec or `.rspec-local`.<br /> #<br /> # The following line is provided for convenience purposes. It has the downside<br /> # of increasing the boot-up time by auto-requiring all files in the support<br /> # directory. Alternatively, in the individual `*_spec.rb` files, manually<br /> # require only the support files necessary. <br /> #<br /> # Dir[Rails.root.join('spec/support/**/*.rb')].each { |f| require f }<br /> #<br /> # Checks for pending migrations before tests are run.<br /> # If you are not using ActiveRecord, you can remove this line.<br /> ActiveRecord::Migration.maintain_test_schema!<br /> RSpec.configure do |config|<br /> # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures<br /> config.fixture_path = &quot;#{::Rails.root}/spec/fixtures&quot;<br /> config.include FactoryGirl::Syntax::Methods<br /> #<br /> # If you're not using ActiveRecord, or you'd prefer not to run each of your<br /> # examples within a transaction, remove the following line or assign false<br /> # instead of true.<br /> # config.use_transactional_fixtures = true<br /> # config.before(:suite) do<br /> # DatabaseCleaner.clean_with(:truncation,:only =&gt; ['users'])<br /> # end<br /> # config.before(:each) do<br /> # DatabaseCleaner.strategy = :transaction<br /> # end<br /> # config.before(:each, :js =&gt; true) do<br /> # DatabaseCleaner.strategy = :truncation<br /> # end<br /> # config.before(:each) do<br /> # DatabaseCleaner.start<br /> # end<br /> #<br /> # RSpec Rails can automatically mix in different behaviours to your tests<br /> # based on their file location, for example enabling you to call `get` and<br /> # `post` in specs under `spec/controllers`.<br /> #<br /> # You can disable this behaviour by removing the line below, and instead<br /> # explicitly tag your specs with their type, e.g.:<br /> #<br /> # RSpec.describe UsersController, :type =&gt; :controller do<br /> # # ...<br /> # end<br /> #<br /> # The different available types are documented in the features, such as in<br /> # https://relishapp.com/rspec/rspec-rails/docs<br /> config.infer_spec_type_from_file_location! <br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=97331 2015-10-30T15:27:41Z

<p>Vpaul: </p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Reviewer Instructions==<br /> ===Clone the reopsitory===<br /> Visit [https://github.com/expertiza/expertiza Github repo] for the repository URL. Make sure you're logged in if you have commit access, because the URL will be different.<br /> <br /> git clone (repository URL)<br /> <br /> See https://help.github.com for help on setting up git, authenticating with SSH keys, and checking out a repository.<br /> <br /> ===Installing Gems (ruby dependencies)===<br /> In the expertiza directory:<br /> <br /> bundle install<br /> <br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> scenario &quot;Create Assignment with Wiki assignment?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_wiki_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Reviews visible to all other reviewers?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_reviews_visible_to_all')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with negative scenario&quot;, :skip_before, :js =&gt; true do<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> click_on('Create')<br /> expect(page).to have_content(&quot;New Assignment&quot;)<br /> end <br /> end <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> ===spec_helper.rb===<br /> # This file was generated by the `rails generate rspec:install` command. Conventionally, all<br /> # specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.<br /> # The generated `.rspec` file contains `--require spec_helper` which will cause<br /> # this file to always be loaded, without a need to explicitly require it in any<br /> # files.<br /> #<br /> # Given that it is always loaded, you are encouraged to keep this file as<br /> # light-weight as possible. Requiring heavyweight dependencies from this file<br /> # will add to the boot time of your test suite on EVERY test run, even for an<br /> # individual file that may not need all of that loaded. Instead, consider making<br /> # a separate helper file that requires the additional dependencies and performs<br /> # the additional setup, and require it from the spec files that actually need<br /> # it.<br /> #<br /> # The `.rspec` file also contains a few flags that are not defaults but that<br /> # users commonly want.<br /> #<br /> # See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration<br /> RSpec.configure do |config|<br /> # rspec-expectations config goes here. You can use an alternate<br /> # assertion/expectation library such as wrong or the stdlib/minitest<br /> # assertions if you prefer.<br /> #<br /> config.expect_with :rspec do |expectations|<br /> # This option will default to `true` in RSpec 4. It makes the `description`<br /> # and `failure_message` of custom matchers include text for helper methods<br /> # defined using `chain`, e.g.:<br /> # be_bigger_than(2).and_smaller_than(4).description<br /> # # =&gt; &quot;be bigger than 2 and smaller than 4&quot;<br /> # ...rather than:<br /> # # =&gt; &quot;be bigger than 2&quot;<br /> expectations.include_chain_clauses_in_custom_matcher_descriptions = true<br /> end<br /> #<br /> # rspec-mocks config goes here. You can use an alternate test double<br /> # library (such as bogus or mocha) by changing the `mock_with` option here.<br /> config.mock_with :rspec do |mocks|<br /> # Prevents you from mocking or stubbing a method that does not exist on<br /> # a real object. This is generally recommended, and will default to<br /> # `true` in RSpec 4.<br /> mocks.verify_partial_doubles = true<br /> end<br /> #<br /> # The settings below are suggested to provide a good initial experience<br /> # with RSpec, but feel free to customize to your heart's content.<br /> =begin<br /> # These two settings work together to allow you to limit a spec run<br /> # to individual examples or groups you care about by tagging them with<br /> # `:focus` metadata. When nothing is tagged with `:focus`, all examples<br /> # get run.<br /> config.filter_run :focus<br /> config.run_all_when_everything_filtered = true<br /> # Allows RSpec to persist some state between runs in order to support<br /> # the `--only-failures` and `--next-failure` CLI options. We recommend<br /> # you configure your source control system to ignore this file.<br /> config.example_status_persistence_file_path = &quot;spec/examples.txt&quot;<br /> # Limits the available syntax to the non-monkey patched syntax that is<br /> # recommended. For more details, see:<br /> # - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax<br /> # - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/<br /> # - http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new__config_option_to_disable_rspeccore_monkey_patching<br /> config.disable_monkey_patching!<br /> # Many RSpec users commonly either run the entire suite or an individual<br /> # file, and it's useful to allow more verbose output when running an<br /> # individual spec file.<br /> if config.files_to_run.one?<br /> # Use the documentation formatter for detailed output,<br /> # unless a formatter has already been configured<br /> # (e.g. via a command-line flag).<br /> config.default_formatter = 'doc'<br /> end<br /> # Print the 10 slowest examples and example groups at the<br /> # end of the spec run, to help surface which specs are running<br /> # particularly slow.<br /> config.profile_examples = 10<br /> # Run specs in random order to surface order dependencies. If you find an<br /> # order dependency and want to debug it, you can fix the order by providing<br /> # the seed, which is printed after each run.<br /> # --seed 1234<br /> config.order = :random<br /> # Seed global randomization in this process using the `--seed` CLI option.<br /> # Setting this allows you to use `--seed` to deterministically reproduce<br /> # test failures related to randomization by passing the same `--seed` value<br /> # as the one that triggered the failure.<br /> Kernel.srand config.seed<br /> =end<br /> end<br /> <br /> ===rails_helper.rb===<br /> <br /> # This file is copied to spec/ when you run 'rails generate rspec:install'<br /> ENV['RAILS_ENV'] ||= 'test'<br /> require File.expand_path('../../config/environment', __FILE__)<br /> # Prevent database truncation if the environment is production<br /> abort(&quot;The Rails environment is running in production mode!&quot;) if Rails.env.production?<br /> require 'spec_helper'<br /> require 'rspec/rails'<br /> # Add additional requires below this line. Rails is not loaded until this point!<br /> #<br /> # Requires supporting ruby files with custom matchers and macros, etc, in<br /> # spec/support/ and its subdirectories. Files matching `spec/**/*_spec.rb` are<br /> # run as spec files by default. This means that files in spec/support that end<br /> # in _spec.rb will both be required and run as specs, causing the specs to be<br /> # run twice. It is recommended that you do not name files matching this glob to<br /> # end with _spec.rb. You can configure this pattern with the --pattern<br /> # option on the command line or in ~/.rspec, .rspec or `.rspec-local`.<br /> #<br /> # The following line is provided for convenience purposes. It has the downside<br /> # of increasing the boot-up time by auto-requiring all files in the support<br /> # directory. Alternatively, in the individual `*_spec.rb` files, manually<br /> # require only the support files necessary. <br /> #<br /> # Dir[Rails.root.join('spec/support/**/*.rb')].each { |f| require f }<br /> #<br /> # Checks for pending migrations before tests are run.<br /> # If you are not using ActiveRecord, you can remove this line.<br /> ActiveRecord::Migration.maintain_test_schema!<br /> RSpec.configure do |config|<br /> # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures<br /> config.fixture_path = &quot;#{::Rails.root}/spec/fixtures&quot;<br /> config.include FactoryGirl::Syntax::Methods<br /> #<br /> # If you're not using ActiveRecord, or you'd prefer not to run each of your<br /> # examples within a transaction, remove the following line or assign false<br /> # instead of true.<br /> # config.use_transactional_fixtures = true<br /> # config.before(:suite) do<br /> # DatabaseCleaner.clean_with(:truncation,:only =&gt; ['users'])<br /> # end<br /> # config.before(:each) do<br /> # DatabaseCleaner.strategy = :transaction<br /> # end<br /> # config.before(:each, :js =&gt; true) do<br /> # DatabaseCleaner.strategy = :truncation<br /> # end<br /> # config.before(:each) do<br /> # DatabaseCleaner.start<br /> # end<br /> #<br /> # RSpec Rails can automatically mix in different behaviours to your tests<br /> # based on their file location, for example enabling you to call `get` and<br /> # `post` in specs under `spec/controllers`.<br /> #<br /> # You can disable this behaviour by removing the line below, and instead<br /> # explicitly tag your specs with their type, e.g.:<br /> #<br /> # RSpec.describe UsersController, :type =&gt; :controller do<br /> # # ...<br /> # end<br /> #<br /> # The different available types are documented in the features, such as in<br /> # https://relishapp.com/rspec/rspec-rails/docs<br /> config.infer_spec_type_from_file_location! <br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VGA&diff=97330 2015-10-30T15:16:50Z

<p>Vpaul: Created page with &quot;{{student sandbox}} ==Introduction== This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rail...&quot;</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> scenario &quot;Create Assignment with Wiki assignment?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_wiki_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Reviews visible to all other reviewers?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_reviews_visible_to_all')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with negative scenario&quot;, :skip_before, :js =&gt; true do<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> click_on('Create')<br /> expect(page).to have_content(&quot;New Assignment&quot;)<br /> end <br /> end <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> ===spec_helper.rb===<br /> # This file was generated by the `rails generate rspec:install` command. Conventionally, all<br /> # specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.<br /> # The generated `.rspec` file contains `--require spec_helper` which will cause<br /> # this file to always be loaded, without a need to explicitly require it in any<br /> # files.<br /> #<br /> # Given that it is always loaded, you are encouraged to keep this file as<br /> # light-weight as possible. Requiring heavyweight dependencies from this file<br /> # will add to the boot time of your test suite on EVERY test run, even for an<br /> # individual file that may not need all of that loaded. Instead, consider making<br /> # a separate helper file that requires the additional dependencies and performs<br /> # the additional setup, and require it from the spec files that actually need<br /> # it.<br /> #<br /> # The `.rspec` file also contains a few flags that are not defaults but that<br /> # users commonly want.<br /> #<br /> # See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration<br /> RSpec.configure do |config|<br /> # rspec-expectations config goes here. You can use an alternate<br /> # assertion/expectation library such as wrong or the stdlib/minitest<br /> # assertions if you prefer.<br /> #<br /> config.expect_with :rspec do |expectations|<br /> # This option will default to `true` in RSpec 4. It makes the `description`<br /> # and `failure_message` of custom matchers include text for helper methods<br /> # defined using `chain`, e.g.:<br /> # be_bigger_than(2).and_smaller_than(4).description<br /> # # =&gt; &quot;be bigger than 2 and smaller than 4&quot;<br /> # ...rather than:<br /> # # =&gt; &quot;be bigger than 2&quot;<br /> expectations.include_chain_clauses_in_custom_matcher_descriptions = true<br /> end<br /> #<br /> # rspec-mocks config goes here. You can use an alternate test double<br /> # library (such as bogus or mocha) by changing the `mock_with` option here.<br /> config.mock_with :rspec do |mocks|<br /> # Prevents you from mocking or stubbing a method that does not exist on<br /> # a real object. This is generally recommended, and will default to<br /> # `true` in RSpec 4.<br /> mocks.verify_partial_doubles = true<br /> end<br /> #<br /> # The settings below are suggested to provide a good initial experience<br /> # with RSpec, but feel free to customize to your heart's content.<br /> =begin<br /> # These two settings work together to allow you to limit a spec run<br /> # to individual examples or groups you care about by tagging them with<br /> # `:focus` metadata. When nothing is tagged with `:focus`, all examples<br /> # get run.<br /> config.filter_run :focus<br /> config.run_all_when_everything_filtered = true<br /> # Allows RSpec to persist some state between runs in order to support<br /> # the `--only-failures` and `--next-failure` CLI options. We recommend<br /> # you configure your source control system to ignore this file.<br /> config.example_status_persistence_file_path = &quot;spec/examples.txt&quot;<br /> # Limits the available syntax to the non-monkey patched syntax that is<br /> # recommended. For more details, see:<br /> # - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax<br /> # - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/<br /> # - http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new__config_option_to_disable_rspeccore_monkey_patching<br /> config.disable_monkey_patching!<br /> # Many RSpec users commonly either run the entire suite or an individual<br /> # file, and it's useful to allow more verbose output when running an<br /> # individual spec file.<br /> if config.files_to_run.one?<br /> # Use the documentation formatter for detailed output,<br /> # unless a formatter has already been configured<br /> # (e.g. via a command-line flag).<br /> config.default_formatter = 'doc'<br /> end<br /> # Print the 10 slowest examples and example groups at the<br /> # end of the spec run, to help surface which specs are running<br /> # particularly slow.<br /> config.profile_examples = 10<br /> # Run specs in random order to surface order dependencies. If you find an<br /> # order dependency and want to debug it, you can fix the order by providing<br /> # the seed, which is printed after each run.<br /> # --seed 1234<br /> config.order = :random<br /> # Seed global randomization in this process using the `--seed` CLI option.<br /> # Setting this allows you to use `--seed` to deterministically reproduce<br /> # test failures related to randomization by passing the same `--seed` value<br /> # as the one that triggered the failure.<br /> Kernel.srand config.seed<br /> =end<br /> end<br /> <br /> ===rails_helper.rb===<br /> <br /> # This file is copied to spec/ when you run 'rails generate rspec:install'<br /> ENV['RAILS_ENV'] ||= 'test'<br /> require File.expand_path('../../config/environment', __FILE__)<br /> # Prevent database truncation if the environment is production<br /> abort(&quot;The Rails environment is running in production mode!&quot;) if Rails.env.production?<br /> require 'spec_helper'<br /> require 'rspec/rails'<br /> # Add additional requires below this line. Rails is not loaded until this point!<br /> #<br /> # Requires supporting ruby files with custom matchers and macros, etc, in<br /> # spec/support/ and its subdirectories. Files matching `spec/**/*_spec.rb` are<br /> # run as spec files by default. This means that files in spec/support that end<br /> # in _spec.rb will both be required and run as specs, causing the specs to be<br /> # run twice. It is recommended that you do not name files matching this glob to<br /> # end with _spec.rb. You can configure this pattern with the --pattern<br /> # option on the command line or in ~/.rspec, .rspec or `.rspec-local`.<br /> #<br /> # The following line is provided for convenience purposes. It has the downside<br /> # of increasing the boot-up time by auto-requiring all files in the support<br /> # directory. Alternatively, in the individual `*_spec.rb` files, manually<br /> # require only the support files necessary. <br /> #<br /> # Dir[Rails.root.join('spec/support/**/*.rb')].each { |f| require f }<br /> #<br /> # Checks for pending migrations before tests are run.<br /> # If you are not using ActiveRecord, you can remove this line.<br /> ActiveRecord::Migration.maintain_test_schema!<br /> RSpec.configure do |config|<br /> # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures<br /> config.fixture_path = &quot;#{::Rails.root}/spec/fixtures&quot;<br /> config.include FactoryGirl::Syntax::Methods<br /> #<br /> # If you're not using ActiveRecord, or you'd prefer not to run each of your<br /> # examples within a transaction, remove the following line or assign false<br /> # instead of true.<br /> # config.use_transactional_fixtures = true<br /> # config.before(:suite) do<br /> # DatabaseCleaner.clean_with(:truncation,:only =&gt; ['users'])<br /> # end<br /> # config.before(:each) do<br /> # DatabaseCleaner.strategy = :transaction<br /> # end<br /> # config.before(:each, :js =&gt; true) do<br /> # DatabaseCleaner.strategy = :truncation<br /> # end<br /> # config.before(:each) do<br /> # DatabaseCleaner.start<br /> # end<br /> #<br /> # RSpec Rails can automatically mix in different behaviours to your tests<br /> # based on their file location, for example enabling you to call `get` and<br /> # `post` in specs under `spec/controllers`.<br /> #<br /> # You can disable this behaviour by removing the line below, and instead<br /> # explicitly tag your specs with their type, e.g.:<br /> #<br /> # RSpec.describe UsersController, :type =&gt; :controller do<br /> # # ...<br /> # end<br /> #<br /> # The different available types are documented in the features, such as in<br /> # https://relishapp.com/rspec/rspec-rails/docs<br /> config.infer_spec_type_from_file_location! <br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015&diff=97329 2015-10-30T15:15:45Z

<p>Vpaul: </p> <hr /> <div>==Writing Assignment 2==<br /> *[[CSC/ECE_517_Fall_2015/sample_page]]<br /> *[[CSC/ECE_517_Fall_2015/ossE1558BGJ]]<br /> *[[CSC/ECE 517 Fall 2015/oss/M1502/AAAASS]]<br /> *[[CSC/ECE 517 Fall 2015/oss/M1503/IntegrateXMLParser]]<br /> *[[CSC/ECE_517_Fall_2015/ossE1568BZHXJS]]<br /> *[[CSC/ECE_517_Fall_2015/ossE1572VGA]]<br /> *[[CSC/ECE_517_Fall_2015/oss_E1573_sap]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1559 rrz]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1570 avr]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1556 CHM]]<br /> *[[CSC/ECE 517 Fall 2015/oss M1504 JJD]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1562 APS]]<br /> *[[CSC/ECE 517 Fall 2015/oss M1501 GSN]]<br /> *[[CSC/ECE 517 Fall 2015/oss M1501 GSN]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1555 GMR]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1552 NRR]]<br /> *[[CSC/ECE 517 Fall 2015/oss E1565 AAJ]]</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VPGMAL&diff=97327 2015-10-30T15:13:31Z

<p>Vpaul: /* spec_helper.rb */</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> scenario &quot;Create Assignment with Wiki assignment?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_wiki_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Reviews visible to all other reviewers?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_reviews_visible_to_all')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with negative scenario&quot;, :skip_before, :js =&gt; true do<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> click_on('Create')<br /> expect(page).to have_content(&quot;New Assignment&quot;)<br /> end <br /> end <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> ===spec_helper.rb===<br /> # This file was generated by the `rails generate rspec:install` command. Conventionally, all<br /> # specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.<br /> # The generated `.rspec` file contains `--require spec_helper` which will cause<br /> # this file to always be loaded, without a need to explicitly require it in any<br /> # files.<br /> #<br /> # Given that it is always loaded, you are encouraged to keep this file as<br /> # light-weight as possible. Requiring heavyweight dependencies from this file<br /> # will add to the boot time of your test suite on EVERY test run, even for an<br /> # individual file that may not need all of that loaded. Instead, consider making<br /> # a separate helper file that requires the additional dependencies and performs<br /> # the additional setup, and require it from the spec files that actually need<br /> # it.<br /> #<br /> # The `.rspec` file also contains a few flags that are not defaults but that<br /> # users commonly want.<br /> #<br /> # See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration<br /> RSpec.configure do |config|<br /> # rspec-expectations config goes here. You can use an alternate<br /> # assertion/expectation library such as wrong or the stdlib/minitest<br /> # assertions if you prefer.<br /> #<br /> config.expect_with :rspec do |expectations|<br /> # This option will default to `true` in RSpec 4. It makes the `description`<br /> # and `failure_message` of custom matchers include text for helper methods<br /> # defined using `chain`, e.g.:<br /> # be_bigger_than(2).and_smaller_than(4).description<br /> # # =&gt; &quot;be bigger than 2 and smaller than 4&quot;<br /> # ...rather than:<br /> # # =&gt; &quot;be bigger than 2&quot;<br /> expectations.include_chain_clauses_in_custom_matcher_descriptions = true<br /> end<br /> #<br /> # rspec-mocks config goes here. You can use an alternate test double<br /> # library (such as bogus or mocha) by changing the `mock_with` option here.<br /> config.mock_with :rspec do |mocks|<br /> # Prevents you from mocking or stubbing a method that does not exist on<br /> # a real object. This is generally recommended, and will default to<br /> # `true` in RSpec 4.<br /> mocks.verify_partial_doubles = true<br /> end<br /> #<br /> # The settings below are suggested to provide a good initial experience<br /> # with RSpec, but feel free to customize to your heart's content.<br /> =begin<br /> # These two settings work together to allow you to limit a spec run<br /> # to individual examples or groups you care about by tagging them with<br /> # `:focus` metadata. When nothing is tagged with `:focus`, all examples<br /> # get run.<br /> config.filter_run :focus<br /> config.run_all_when_everything_filtered = true<br /> # Allows RSpec to persist some state between runs in order to support<br /> # the `--only-failures` and `--next-failure` CLI options. We recommend<br /> # you configure your source control system to ignore this file.<br /> config.example_status_persistence_file_path = &quot;spec/examples.txt&quot;<br /> # Limits the available syntax to the non-monkey patched syntax that is<br /> # recommended. For more details, see:<br /> # - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax<br /> # - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/<br /> # - http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new__config_option_to_disable_rspeccore_monkey_patching<br /> config.disable_monkey_patching!<br /> # Many RSpec users commonly either run the entire suite or an individual<br /> # file, and it's useful to allow more verbose output when running an<br /> # individual spec file.<br /> if config.files_to_run.one?<br /> # Use the documentation formatter for detailed output,<br /> # unless a formatter has already been configured<br /> # (e.g. via a command-line flag).<br /> config.default_formatter = 'doc'<br /> end<br /> # Print the 10 slowest examples and example groups at the<br /> # end of the spec run, to help surface which specs are running<br /> # particularly slow.<br /> config.profile_examples = 10<br /> # Run specs in random order to surface order dependencies. If you find an<br /> # order dependency and want to debug it, you can fix the order by providing<br /> # the seed, which is printed after each run.<br /> # --seed 1234<br /> config.order = :random<br /> # Seed global randomization in this process using the `--seed` CLI option.<br /> # Setting this allows you to use `--seed` to deterministically reproduce<br /> # test failures related to randomization by passing the same `--seed` value<br /> # as the one that triggered the failure.<br /> Kernel.srand config.seed<br /> =end<br /> end<br /> <br /> ===rails_helper.rb===<br /> <br /> # This file is copied to spec/ when you run 'rails generate rspec:install'<br /> ENV['RAILS_ENV'] ||= 'test'<br /> require File.expand_path('../../config/environment', __FILE__)<br /> # Prevent database truncation if the environment is production<br /> abort(&quot;The Rails environment is running in production mode!&quot;) if Rails.env.production?<br /> require 'spec_helper'<br /> require 'rspec/rails'<br /> # Add additional requires below this line. Rails is not loaded until this point!<br /> #<br /> # Requires supporting ruby files with custom matchers and macros, etc, in<br /> # spec/support/ and its subdirectories. Files matching `spec/**/*_spec.rb` are<br /> # run as spec files by default. This means that files in spec/support that end<br /> # in _spec.rb will both be required and run as specs, causing the specs to be<br /> # run twice. It is recommended that you do not name files matching this glob to<br /> # end with _spec.rb. You can configure this pattern with the --pattern<br /> # option on the command line or in ~/.rspec, .rspec or `.rspec-local`.<br /> #<br /> # The following line is provided for convenience purposes. It has the downside<br /> # of increasing the boot-up time by auto-requiring all files in the support<br /> # directory. Alternatively, in the individual `*_spec.rb` files, manually<br /> # require only the support files necessary. <br /> #<br /> # Dir[Rails.root.join('spec/support/**/*.rb')].each { |f| require f }<br /> #<br /> # Checks for pending migrations before tests are run.<br /> # If you are not using ActiveRecord, you can remove this line.<br /> ActiveRecord::Migration.maintain_test_schema!<br /> RSpec.configure do |config|<br /> # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures<br /> config.fixture_path = &quot;#{::Rails.root}/spec/fixtures&quot;<br /> config.include FactoryGirl::Syntax::Methods<br /> #<br /> # If you're not using ActiveRecord, or you'd prefer not to run each of your<br /> # examples within a transaction, remove the following line or assign false<br /> # instead of true.<br /> # config.use_transactional_fixtures = true<br /> # config.before(:suite) do<br /> # DatabaseCleaner.clean_with(:truncation,:only =&gt; ['users'])<br /> # end<br /> # config.before(:each) do<br /> # DatabaseCleaner.strategy = :transaction<br /> # end<br /> # config.before(:each, :js =&gt; true) do<br /> # DatabaseCleaner.strategy = :truncation<br /> # end<br /> # config.before(:each) do<br /> # DatabaseCleaner.start<br /> # end<br /> #<br /> # RSpec Rails can automatically mix in different behaviours to your tests<br /> # based on their file location, for example enabling you to call `get` and<br /> # `post` in specs under `spec/controllers`.<br /> #<br /> # You can disable this behaviour by removing the line below, and instead<br /> # explicitly tag your specs with their type, e.g.:<br /> #<br /> # RSpec.describe UsersController, :type =&gt; :controller do<br /> # # ...<br /> # end<br /> #<br /> # The different available types are documented in the features, such as in<br /> # https://relishapp.com/rspec/rspec-rails/docs<br /> config.infer_spec_type_from_file_location! <br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VPGMAL&diff=97324 2015-10-30T15:07:07Z

<p>Vpaul: /* Code */</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> scenario &quot;Create Assignment with Wiki assignment?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_wiki_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Reviews visible to all other reviewers?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_reviews_visible_to_all')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with negative scenario&quot;, :skip_before, :js =&gt; true do<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> click_on('Create')<br /> expect(page).to have_content(&quot;New Assignment&quot;)<br /> end <br /> end <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> ===spec_helper.rb===<br /> <br /> ===rails_helper.rb===<br /> <br /> # This file is copied to spec/ when you run 'rails generate rspec:install'<br /> ENV['RAILS_ENV'] ||= 'test'<br /> require File.expand_path('../../config/environment', __FILE__)<br /> # Prevent database truncation if the environment is production<br /> abort(&quot;The Rails environment is running in production mode!&quot;) if Rails.env.production?<br /> require 'spec_helper'<br /> require 'rspec/rails'<br /> # Add additional requires below this line. Rails is not loaded until this point!<br /> #<br /> # Requires supporting ruby files with custom matchers and macros, etc, in<br /> # spec/support/ and its subdirectories. Files matching `spec/**/*_spec.rb` are<br /> # run as spec files by default. This means that files in spec/support that end<br /> # in _spec.rb will both be required and run as specs, causing the specs to be<br /> # run twice. It is recommended that you do not name files matching this glob to<br /> # end with _spec.rb. You can configure this pattern with the --pattern<br /> # option on the command line or in ~/.rspec, .rspec or `.rspec-local`.<br /> #<br /> # The following line is provided for convenience purposes. It has the downside<br /> # of increasing the boot-up time by auto-requiring all files in the support<br /> # directory. Alternatively, in the individual `*_spec.rb` files, manually<br /> # require only the support files necessary. <br /> #<br /> # Dir[Rails.root.join('spec/support/**/*.rb')].each { |f| require f }<br /> #<br /> # Checks for pending migrations before tests are run.<br /> # If you are not using ActiveRecord, you can remove this line.<br /> ActiveRecord::Migration.maintain_test_schema!<br /> RSpec.configure do |config|<br /> # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures<br /> config.fixture_path = &quot;#{::Rails.root}/spec/fixtures&quot;<br /> config.include FactoryGirl::Syntax::Methods<br /> #<br /> # If you're not using ActiveRecord, or you'd prefer not to run each of your<br /> # examples within a transaction, remove the following line or assign false<br /> # instead of true.<br /> # config.use_transactional_fixtures = true<br /> # config.before(:suite) do<br /> # DatabaseCleaner.clean_with(:truncation,:only =&gt; ['users'])<br /> # end<br /> # config.before(:each) do<br /> # DatabaseCleaner.strategy = :transaction<br /> # end<br /> # config.before(:each, :js =&gt; true) do<br /> # DatabaseCleaner.strategy = :truncation<br /> # end<br /> # config.before(:each) do<br /> # DatabaseCleaner.start<br /> # end<br /> #<br /> # RSpec Rails can automatically mix in different behaviours to your tests<br /> # based on their file location, for example enabling you to call `get` and<br /> # `post` in specs under `spec/controllers`.<br /> #<br /> # You can disable this behaviour by removing the line below, and instead<br /> # explicitly tag your specs with their type, e.g.:<br /> #<br /> # RSpec.describe UsersController, :type =&gt; :controller do<br /> # # ...<br /> # end<br /> #<br /> # The different available types are documented in the features, such as in<br /> # https://relishapp.com/rspec/rspec-rails/docs<br /> config.infer_spec_type_from_file_location! <br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VPGMAL&diff=97323 2015-10-30T15:04:36Z

<p>Vpaul: /* Code */</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> scenario &quot;Create Assignment with Wiki assignment?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_wiki_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Reviews visible to all other reviewers?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_reviews_visible_to_all')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with negative scenario&quot;, :skip_before, :js =&gt; true do<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> click_on('Create')<br /> expect(page).to have_content(&quot;New Assignment&quot;)<br /> end <br /> end <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> ===spec_helper.rb===<br /> <br /> ===rails_helper.rb===<br /> <br /> # This file is copied to spec/ when you run 'rails generate rspec:install'<br /> ENV['RAILS_ENV'] ||= 'test'<br /> require File.expand_path('../../config/environment', __FILE__)<br /> # Prevent database truncation if the environment is production<br /> abort(&quot;The Rails environment is running in production mode!&quot;) if Rails.env.production?<br /> require 'spec_helper'<br /> require 'rspec/rails'<br /> # Add additional requires below this line. Rails is not loaded until this point!<br /> <br /> # Requires supporting ruby files with custom matchers and macros, etc, in<br /> # spec/support/ and its subdirectories. Files matching `spec/**/*_spec.rb` are<br /> # run as spec files by default. This means that files in spec/support that end<br /> # in _spec.rb will both be required and run as specs, causing the specs to be<br /> # run twice. It is recommended that you do not name files matching this glob to<br /> # end with _spec.rb. You can configure this pattern with the --pattern<br /> # option on the command line or in ~/.rspec, .rspec or `.rspec-local`.<br /> #<br /> # The following line is provided for convenience purposes. It has the downside<br /> # of increasing the boot-up time by auto-requiring all files in the support<br /> # directory. Alternatively, in the individual `*_spec.rb` files, manually<br /> # require only the support files necessary. <br /> #<br /> # Dir[Rails.root.join('spec/support/**/*.rb')].each { |f| require f }<br /> <br /> # Checks for pending migrations before tests are run.<br /> # If you are not using ActiveRecord, you can remove this line.<br /> ActiveRecord::Migration.maintain_test_schema!<br /> <br /> RSpec.configure do |config|<br /> # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures<br /> config.fixture_path = &quot;#{::Rails.root}/spec/fixtures&quot;<br /> config.include FactoryGirl::Syntax::Methods<br /> <br /> # If you're not using ActiveRecord, or you'd prefer not to run each of your<br /> # examples within a transaction, remove the following line or assign false<br /> # instead of true.<br /> # config.use_transactional_fixtures = true<br /> <br /> # config.before(:suite) do<br /> # DatabaseCleaner.clean_with(:truncation,:only =&gt; ['users'])<br /> # end<br /> <br /> # config.before(:each) do<br /> # DatabaseCleaner.strategy = :transaction<br /> # end<br /> <br /> # config.before(:each, :js =&gt; true) do<br /> # DatabaseCleaner.strategy = :truncation<br /> # end<br /> <br /> # config.before(:each) do<br /> # DatabaseCleaner.start<br /> # end<br /> <br /> <br /> # RSpec Rails can automatically mix in different behaviours to your tests<br /> # based on their file location, for example enabling you to call `get` and<br /> # `post` in specs under `spec/controllers`.<br /> #<br /> # You can disable this behaviour by removing the line below, and instead<br /> # explicitly tag your specs with their type, e.g.:<br /> #<br /> # RSpec.describe UsersController, :type =&gt; :controller do<br /> # # ...<br /> # end<br /> #<br /> # The different available types are documented in the features, such as in<br /> # https://relishapp.com/rspec/rspec-rails/docs<br /> config.infer_spec_type_from_file_location! <br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VPGMAL&diff=97322 2015-10-30T15:02:14Z

<p>Vpaul: </p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> scenario &quot;Create Assignment with Wiki assignment?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_wiki_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Reviews visible to all other reviewers?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_reviews_visible_to_all')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with negative scenario&quot;, :skip_before, :js =&gt; true do<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> click_on('Create')<br /> expect(page).to have_content(&quot;New Assignment&quot;)<br /> end <br /> end <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> ===spec_helper.rb===<br /> <br /> ===rails_helper.rb===<br /> <br /> # This file is copied to spec/ when you run 'rails generate rspec:install'<br /> ENV['RAILS_ENV'] ||= 'test'<br /> require File.expand_path('../../config/environment', __FILE__)<br /> # Prevent database truncation if the environment is production<br /> abort(&quot;The Rails environment is running in production mode!&quot;) if Rails.env.production?<br /> require 'spec_helper'<br /> require 'rspec/rails'<br /> # Add additional requires below this line. Rails is not loaded until this point!<br /> <br /> # Requires supporting ruby files with custom matchers and macros, etc, in<br /> # spec/support/ and its subdirectories. Files matching `spec/**/*_spec.rb` are<br /> # run as spec files by default. This means that files in spec/support that end<br /> # in _spec.rb will both be required and run as specs, causing the specs to be<br /> # run twice. It is recommended that you do not name files matching this glob to<br /> # end with _spec.rb. You can configure this pattern with the --pattern<br /> # option on the command line or in ~/.rspec, .rspec or `.rspec-local`.<br /> #<br /> # The following line is provided for convenience purposes. It has the downside<br /> # of increasing the boot-up time by auto-requiring all files in the support<br /> # directory. Alternatively, in the individual `*_spec.rb` files, manually<br /> # require only the support files necessary.<br /> #<br /> # Dir[Rails.root.join('spec/support/**/*.rb')].each { |f| require f }<br /> <br /> # Checks for pending migrations before tests are run.<br /> # If you are not using ActiveRecord, you can remove this line.<br /> ActiveRecord::Migration.maintain_test_schema!<br /> <br /> RSpec.configure do |config|<br /> # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures<br /> config.fixture_path = &quot;#{::Rails.root}/spec/fixtures&quot;<br /> config.include FactoryGirl::Syntax::Methods<br /> <br /> # If you're not using ActiveRecord, or you'd prefer not to run each of your<br /> # examples within a transaction, remove the following line or assign false<br /> # instead of true.<br /> # config.use_transactional_fixtures = true<br /> <br /> # config.before(:suite) do<br /> # DatabaseCleaner.clean_with(:truncation,:only =&gt; ['users'])<br /> # end<br /> <br /> # config.before(:each) do<br /> # DatabaseCleaner.strategy = :transaction<br /> # end<br /> <br /> # config.before(:each, :js =&gt; true) do<br /> # DatabaseCleaner.strategy = :truncation<br /> # end<br /> <br /> # config.before(:each) do<br /> # DatabaseCleaner.start<br /> # end<br /> <br /> <br /> # RSpec Rails can automatically mix in different behaviours to your tests<br /> # based on their file location, for example enabling you to call `get` and<br /> # `post` in specs under `spec/controllers`.<br /> #<br /> # You can disable this behaviour by removing the line below, and instead<br /> # explicitly tag your specs with their type, e.g.:<br /> #<br /> # RSpec.describe UsersController, :type =&gt; :controller do<br /> # # ...<br /> # end<br /> #<br /> # The different available types are documented in the features, such as in<br /> # https://relishapp.com/rspec/rspec-rails/docs<br /> config.infer_spec_type_from_file_location! <br /> end</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VPGMAL&diff=97321 2015-10-30T15:00:04Z

<p>Vpaul: </p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> scenario &quot;Create Assignment with Wiki assignment?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_wiki_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Reviews visible to all other reviewers?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_reviews_visible_to_all')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with negative scenario&quot;, :skip_before, :js =&gt; true do<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> click_on('Create')<br /> expect(page).to have_content(&quot;New Assignment&quot;)<br /> end <br /> end <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> ===spec_helper.rb===<br /> <br /> ===rails_helper.rb===</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VPGMAL&diff=97320 2015-10-30T14:59:30Z

<p>Vpaul: </p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> scenario &quot;Create Assignment with Wiki assignment?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_wiki_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Reviews visible to all other reviewers?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_reviews_visible_to_all')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with negative scenario&quot;, :skip_before, :js =&gt; true do<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> click_on('Create')<br /> expect(page).to have_content(&quot;New Assignment&quot;)<br /> end <br /> end <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> <br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> ===spec_helper.rb===<br /> <br /> ===rails_helper.rb===</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VPGMAL&diff=97319 2015-10-30T14:58:28Z

<p>Vpaul: </p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> scenario &quot;Create Assignment with Wiki assignment?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_wiki_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Reviews visible to all other reviewers?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_reviews_visible_to_all')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with negative scenario&quot;, :skip_before, :js =&gt; true do<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> click_on('Create')<br /> expect(page).to have_content(&quot;New Assignment&quot;)<br /> end <br /> end <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> ===spec_helper.rb===<br /> <br /> ===rails_helper.rb===</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VPGMAL&diff=97318 2015-10-30T14:56:51Z

<p>Vpaul: </p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases for the creation of a private assignment.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> scenario &quot;Create Assignment with Wiki assignment?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_wiki_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Reviews visible to all other reviewers?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_reviews_visible_to_all')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with negative scenario&quot;, :skip_before, :js =&gt; true do<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> click_on('Create')<br /> expect(page).to have_content(&quot;New Assignment&quot;)<br /> end <br /> end <br /> <br /> The test cases written also contain tests for the creation of public assignments. Listed below are the following tests. Once again we need to sign in the instructor before he can create any assignments.<br /> <br /> RSpec.feature &quot;create public assignment&quot; do<br /> before(:each) do<br /> #@user = FactoryGirl.create(:user)<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> end<br /> end<br /> scenario &quot;Create Assignment has teams&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('team_assignment')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment has quiz&quot;,:js =&gt; true do <br /> click_button 'New public assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> check('assignment_form_assignment_require_quiz')<br /> check('assignment_form_assignment_availability_flag')<br /> #find(:xpath, &quot;//input[@id='']&quot;).set &quot;0&quot;<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> ===spec_helper.rb===<br /> <br /> ===rails_helper.rb===</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VPGMAL&diff=97317 2015-10-30T14:50:32Z

<p>Vpaul: </p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> scenario &quot;Create Assignment with Wiki assignment?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_wiki_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> <br /> ===spec_helper.rb===<br /> <br /> ===rails_helper.rb===</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VPGMAL&diff=97316 2015-10-30T14:47:32Z

<p>Vpaul: </p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> Given above is a portion of the code which we have to execute before testing each scenario. This is encapsulated within before(:each). In order to be able to create assignments, the instructor has to first login. So we set up the environment of logging in in the before(:each) block and navigating to the page where assignments can be created.<br /> <br /> We have written a total of 27 test cases in the assignment_creation.rb testing all the permutations and combinations with which an instructor can create an assignment. Listed below are a few of those test cases.<br /> <br /> scenario &quot;Create Assignment with Has teams?&quot;, :js =&gt; true do <br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('team_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> scenario &quot;Create Assignment with Has quiz?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_form_assignment_require_quiz')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> <br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end <br /> <br /> scenario &quot;Create Assignment with Wiki assignment?&quot;, :js =&gt; true do<br /> uncheck('assignment_form_assignment_availability_flag')<br /> check('assignment_wiki_assignment')<br /> click_on('Create')<br /> click_on('Rubrics')<br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]').first()<br /> end<br /> <br /> within('#questionnaire_table_ReviewQuestionnaire') do<br /> select('Animation', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> within('#questionnaire_table_AuthorFeedbackQuestionnaire') do<br /> select('Author feedback OTD1', from: 'assignment_form[assignment_questionnaire][][questionnaire_id]')<br /> end<br /> expect(page).to have_content(&quot;Rubrics&quot;)<br /> click_on('submit_btn')<br /> expect(page).to have_content(&quot;successfully&quot;,:wait=&gt;5)<br /> end<br /> <br /> <br /> ===spec_helper.rb===<br /> <br /> ===rails_helper.rb===</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VPGMAL&diff=97315 2015-10-30T14:34:04Z

<p>Vpaul: /* Code */</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> <br /> ===spec_helper.rb===<br /> <br /> ===rails_helper.rb===</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VPGMAL&diff=97314 2015-10-30T14:33:24Z

<p>Vpaul: /* Code */</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> <br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> <br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> <br /> ===spec_helper.rb===<br /> <br /> ===rails_helper.rb===</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VPGMAL&diff=97232 2015-10-28T05:25:32Z

<p>Vpaul: /* assignment_creation.rb */</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> &lt;syntaxhighlight lang='ruby'&gt;<br /> require 'rails_helper'<br /> require 'spec_helper'<br /> <br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> <br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> &lt;/syntaxhighlight&gt;<br /> <br /> ===spec_helper.rb===<br /> <br /> ===rails_helper.rb===</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VPGMAL&diff=97231 2015-10-28T05:23:56Z

<p>Vpaul: /* assignment_creation.rb */</p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> &lt;syntaxhighlight lang=&quot;ruby&quot;&gt;<br /> require 'rails_helper'<br /> require 'spec_helper'<br /> <br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> <br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> &lt;/syntaxhighlight&gt;<br /> <br /> ===spec_helper.rb===<br /> <br /> ===rails_helper.rb===</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VPGMAL&diff=97230 2015-10-28T05:23:25Z

<p>Vpaul: </p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> &lt;syntaxhighlight lang=&quot;ruby&quot;&gt;<br /> require 'rails_helper'<br /> require 'spec_helper'<br /> <br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> <br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> &lt;/syntaxhighlight&gt;<br /> ===spec_helper.rb===<br /> <br /> ===rails_helper.rb===</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VPGMAL&diff=97229 2015-10-28T05:21:03Z

<p>Vpaul: </p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> &lt;source lang='ruby'&gt;<br /> require 'rails_helper'<br /> require 'spec_helper'<br /> <br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> <br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> &lt;/source&gt;<br /> ===spec_helper.rb===<br /> <br /> ===rails_helper.rb===</div>

Vpaul https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2015/ossE1572VPGMAL&diff=97228 2015-10-28T05:14:59Z

<p>Vpaul: </p> <hr /> <div>{{student sandbox}}<br /> ==Introduction==<br /> This page provides a description of the Expertiza based OSS project. Expertiza is an open source rails application developed on ruby and rails. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc). The instructors can create assignments using this application and customize and manage them. It also helps to introduce the peer review system by which students can review the projects of their colleagues.<br /> <br /> ==Problem Statement==<br /> We were expected to write a feature test which mocks the creation of an Assignment. For Expertiza Assignment management is the central part of the workflow. <br /> Goals:<br /> # Understand the flow of the Assignment creation by instructor manually.<br /> # Mock the same steps using capybara<br /> # Create multiple assignments with different options and testing their existence.<br /> <br /> ==Project Links==<br /> <br /> * [http://www.wikipedia.org Github repo]<br /> * [http://www.wikipedia.org Expertiza pull request]<br /> * [http://www.wikipedia.org Youtube video manual]<br /> <br /> ==Classes Involved==<br /> * assignment_creation.rb<br /> * spec_helper.rb<br /> * rails_helper.rb<br /> <br /> The assignment_creation.rb contains the feature tests written to test the creation of the assignment. The rails_helper is copied to spec/ when you run 'rails generate rspec:install'. All the rspec-expectations config goes into the spec_helper_file. We have used Capybara and RSpec to test our application. Capybara helps you test web applications by simulating how a real user would interact with your app. <br /> <br /> ==Code==<br /> ===assignment_creation.rb===<br /> <br /> require 'rails_helper'<br /> require 'spec_helper'<br /> <br /> def GenerateAssignmentName()<br /> (rand(1000) + 1).to_s + 'RSpecID' + (1 + rand(1000)).to_s<br /> end<br /> <br /> RSpec.feature &quot;create private assignment&quot; do<br /> before(:each) do |example|<br /> unless example.metadata[:skip_before]<br /> visit root_path<br /> fill_in('login_name', :with =&gt; 'instructor6')<br /> fill_in('login_password', :with =&gt; 'password')<br /> click_on('SIGN IN')<br /> expect(page).to have_content('Manage')<br /> within(&quot;.content&quot;) do<br /> click_on(&quot;Assignments&quot;)<br /> click_button 'New private assignment'<br /> fill_in('assignment_form_assignment_name',:with =&gt; GenerateAssignmentName())<br /> select('CSC 517 Fall 2010', from: 'assignment_form_assignment_course_id')<br /> fill_in('assignment_form_assignment_directory_path',:with =&gt; '/')<br /> fill_in('assignment_form_assignment_spec_location',:with =&gt; 'google.com')<br /> end<br /> end <br /> end<br /> <br /> ===spec_helper.rb===<br /> <br /> ===rails_helper.rb===</div>

Vpaul