team 10 - rsanchez-wsu/jfiles GitHub Wiki

In this milestone, we will be focused on making sure everyone has complete understanding of how to navigate and use GitHub and resolve any technical issues that our fellow teammates are struggling with. This will include how to clone the GitHub repository into eclipse as well as upload and commit changes onto GitHub. We will also need to know how to navigate and use the various sections on GitHub such as milestones, branches, wiki, and issues. Next, we will also want to aim our focus on starting a tutorial wiki to help others who will take this course in the future. This will be an ongoing project and will require communication throughout our team in order to take the best approach on completion of this task. We should first start by creating a test class with several methods in order to test the functions of the main. This will help us to fill out our wiki page with the results of the tests. Finally, we will attempt to work on issue #213 as well as discuss other possible issues that we could resolve. Also, remember to post on slack in order to inform the group on any progress you are making.

Milestone #2

In this milestone, we will be focusing on the issues #244, #245, and #246 all of which are carry overs from milestone 1. For Issue #244 progress should continue to be made on the various tests of the main. We will eventually need to start using JUnit to get more detailed information through testing. For issue #246, which is similar in description to issue #244, the description should be changed in order to focus on improving the readability and overall helpfulness to new users of the tutorial page. I believe an introduction to the page explaining the overall goal and some basic functions of eclipse would help. We could also improve introductions for the various tests. For issue #245, we will need to start to flesh out more details for the wiki, as well as merge the formatting from the excel sheet to the main wiki page through editing. We will also continue issue #213 from milestone 1. Progress was made in fixing the errors, and we will soon be able to close the issue.

Milestone #3

In this milestone, we will be continuing our focus on our wiki page and testing. We will need to create an issue that will outline our process for testing with JUnit. This could include what we should be testing first as well as a designated wiki page for information on our results. We will also need to create an issue that deals with integrating it into our developmental branch. Issue #244 has a similar goal in mind, and can be carried over into this milestone. Issue #260 was added during the week and will carry it over from the previous milestone. Finally, we will want to create an issue about creating more tutorials, and we will be able to comment on the issue about tutorials we are working on. With all of these new Objects we will want to add them to the milestone after creation. in addition, Feel free to assign yourself to any of them and multiple people can tackle the same issue.

Milestone #4

In this milestone, we will be continuing are work with testing with the help of JUnit. We have made much progress as we have implemented a test folder currently have several classes testing the server by Laurence. Team 5 is also using JUnit for testing and the merging of the branches. This issue is stated in #290. Currently, there are several issues addressing this in #279 and #260. I believe these issues could use more information within the test classes themselves and possibly more information on the overall process of the test on the issue pages. However, they are great starts to the overall testing process. More issues can be created for other test classes as we begin to create them. Carrying over issue #277 from milestone 3, we will need to expand our JUnit page with information from our test classes. Scott will also be working on a slackbot with the overall goal to link updates from github into slack.

Milestone #5

In this milestone, we will be mostly carrying over our work from our previous milestone as we are making progress in our current test classes. Issue #294 will be our overall goals for implementing tests as they cover a number of issues that would deal with writing these Test classes. Make sure to refer to them when writing a test class as you will be able to update and comment on those issues as necessary. Also with the progress being made, we could update our wiki page with various explanations and overall goals as well as expand on the JUnit page explained in issue #277. Laurence will continue his work, which he has done a lot of in the past few weeks, in issue #260, #286, and #287. Furthermore, we will continue our work on merging files with team 5 tests in issue #290, and the work on the slackbot in issue #285 by Scott. Since this is spring break week will have awhile before the next milestone, and it’s understandable for the work pace to be hindered by this break. Have a good spring break team.

Milestone #6

In this milestone, we will continue building our test classes and editing our current ones with more functionality. We will be carrying over issues #309, #304, #294, #287, #285, #335 and #277 from milestone 5. One idea would be to start implementing other commands to test on the server similar to our test LS class that was created by laurenceforshaw. I do believe our wiki page can be filled out a bit more on information regarding some of the tests that have been created, and this could be tackled by anyone. In addition, Laurence has gotten JUnit to auto run through ant, but needs others to test this out to see if they can get it working as well. Cameron wants to look into the GUI aspect and will be writing suggestions and documentation about that aspect of the design. Scott is still working on his slackbot idea. A wiki page with possible concepts or limitations to this idea could help aid in the developmental process. Finally, as we are in the middle of the term, new ideas are welcomed in our direction of our overall goal. Feel free to post any of these ideas in slack or create a wiki page to conceptualize them.

Milestone #7

In this milestone, we have several different tasks that individuals in our group have decided to branch out on more away from testing. However, some of us will continue on creating and refining our test classes. Issues will need to be created for some of the new work that we will be creating this week. For the issues we are carrying over include issue #277, #285, #294, and #309. Laurence will be working on the database aspect with comments and testing. In addition, we still need a wiki page that underlines the steps to auto running ant, with any success or failures to document your work on this process. This is stated in issue #277 and will be closed afterword’s. Cera will be continuing her work on her test arguments, and expanding the classes that she has created. Mark will be working on a xml test class to test the various aspects of the xml handler. Cameron will be digging deeper into the GUI portion of the project with documentation of the current implementation. Luke will be working be continue his work on his test class implementations. Scott will be continuing his work on his slackbot. Once again, feel free to create any issue with a fair amount of detail to explain the current tasks that you will be working on.

Milestone #8

In this milestone, we will be continuing most of the work that was started in our previous milestone. For the issues we are carrying over include issue #277, #285, #294, #309, #347, and #351. Laurence will be continuing his work on the database, and be adding documentation to the wiki. Cera will be continuing her work on her test arguments, and also be integrating them to work with some of Laurence’s tests. Mark will be working on a xml test class. Cameron will be working on the wiki aspects of the GUI and possibly another documentation that could be added. Luke will continue his work on his test class implementations, and be correcting errors in previously written wikis and classes. Scott will be continuing his work on his slackbot. We also should look into merging our code with the master. Once again, feel free to create any issue with a fair amount of detail to explain the current tasks that you will be working on.

Milestone #9

In this milestone, we will be continuing most of the work that was started in our previous milestone. For the issues we are carrying over include issue #277, #294, #309, #347, and #351. Laurence will be working with database and user functions. Cera will be continuing her work on her test arguments, and be working with Laurence with testing auto run with ant. Mark will be continuing his work with xml handler test class. Cameron will be working with the GUI side through documentation, and will be looking to help anyone else out on their development. Luke will continue his work on his test class implementations, and to manage our updates accordingly. Once again, feel free to create any issue with a fair amount of detail to explain the current tasks that you will be working on.

Milestone #10

In this milestone, we will be trying to finish our issues by the end of the week. For the issues we are carrying over include issue #277, #294, #309, #351, #353, and #367. This is the final week to work on these issues, and I encourage everyone to try and close out the issues if we can. Most of these issues are partially completed, and just need some finishing up. The documentation issues should be easy to finish, and we can edit our wiki page for any errors. Also, we should merge our branch to the master, and hopefully this isn't a huge problem as our class files are fairly independent.

team 10 - rsanchez-wsu/jfiles GitHub Wiki

Contact Listing:

Developement

Ideas

Work in Progress

Milestones

Milestone #1