davidpeterko cs378-deque issues

davidpeterko / cs378-deque

cs378 project 4 deque

0 stars 0 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

transferring travis ci url to my aprtner

#22 davidpeterko opened 9 years ago
1
make the public test cases

#21 imasrur closed 9 years ago
0
get the sha

#20 imasrur closed 9 years ago
0
check the right amount of cases

#19 imasrur closed 9 years ago
0
make the log

#18 imasrur closed 9 years ago
0
make sure to have enough test

#17 imasrur closed 9 years ago
0
travis be good

#16 imasrur closed 9 years ago
0
make the html

#15 imasrur closed 9 years ago
0
make resize for new array

#14 imasrur closed 9 years ago
0
make sure resize work for greater than the the array size

#13 imasrur closed 9 years ago
0
edge cases for plus plus and -- in the iterator

#12 imasrur closed 9 years ago
0
insert the resize in push back and push front

#11 imasrur closed 9 years ago
0
(Requirement #10) Run Doxygen, which will create html/ [make html], that then documents the interfaces to your functions.

#10 davidpeterko closed 9 years ago
0
(Requirement #9) Possibly implement and debug the an improvement until all tests pass, and add, commit, and push to the private code repo.

#9 davidpeterko closed 9 years ago
0
(Requirement #8) Copy your unit tests and to your clone of the public test repo, rename the files, do a git pull to synchronize your clone, and then add, commit and push to the public test repo.

#8 davidpeterko closed 9 years ago
0
(Requirement #7) Clone the public test repo onto your local directory [make deque-tests].

#7 davidpeterko closed 9 years ago
0
(Requirement #6) Implement and debug the simplest possible solution in Deque.h with assertions that check pre-conditions, post-conditions, argument validity, and return-value validity, until all tests pass, and add, commit, and push to the private code repo.

#6 davidpeterko closed 9 years ago
0
(Requirement #5) Write unit tests in TestDeque.c++ that test corner cases and failure cases until you have an average of 3 tests for each function, confirm the expected failures, and add, commit, and push to the private code repo.

#5 davidpeterko closed 9 years ago
0
(Requirement #4) Only merge with the master after a successful build at Travis CI.

#4 davidpeterko closed 9 years ago
0
(Requirement #3) Connect your Travis CI account to the dev branch of your private code repo.

#3 davidpeterko closed 9 years ago
0
(Requirement #2) Clone your private code repo onto your local directory.

#2 davidpeterko closed 9 years ago
0
(Requirement #1) Estimated time completion

#1 davidpeterko closed 9 years ago
0