mirror of https://github.com/01-edu/public.git
MSilva95
5 years ago
3 changed files with 213 additions and 108 deletions
@ -1,53 +1,53 @@
|
||||
#### Functional Project Questions |
||||
|
||||
##### Try passing as arguments `"left" --align=right` |
||||
###### Does it displays the expected result? |
||||
###### Does it displays the correct result at the right side? |
||||
##### Try passing as arguments `"right" --align=left` |
||||
###### Does it displays the expected result? |
||||
###### Does it displays the correct result at the left side? |
||||
##### Try passing as arguments `"hello" --align=center` |
||||
###### Does it displays the expected result? |
||||
###### Does it displays the correct result at the center? |
||||
##### Try passing as arguments `"1 Two 4" --align=justify` |
||||
###### Does it displays the expected result? |
||||
###### Does it displays the correct result justified? |
||||
##### Try passing as arguments `"23/32" --align=right` |
||||
###### Does it displays the expected result? |
||||
###### Does it displays the correct result at the right side? |
||||
##### Try passing as arguments `"ABCabc123" --align=right` |
||||
###### Does it displays the expected result? |
||||
###### Does it displays the correct result at the right side? |
||||
##### Try passing as arguments `"!#$%&" --align=center` |
||||
###### Does it displays the expected result? |
||||
###### Does it displays the correct result at the center? |
||||
##### Try passing as arguments `"23Hello World!" --align=left` |
||||
###### Does it displays the expected result? |
||||
###### Does it displays the correct result at the left side? |
||||
##### Try passing as arguments `"HELLO there HOW are YOU?!" --align=justify` |
||||
###### Does it displays the expected result? |
||||
###### Does it displays the correct result justified? |
||||
##### Try passing as arguments `"a -> A b -> B c -> C" --align=right` |
||||
###### Does it displays the expected result? |
||||
###### Does it displays the correct result at the right side? |
||||
|
||||
#### Basic |
||||
|
||||
###### *Does the code present commenting ? (https://github.com/01-edu/public/blob/master/subjects/good-practices.en.md) |
||||
###### *Does the code present documentation ? |
||||
###### *Does it present consistent indentation ? |
||||
###### *Does the code avoid obvious comments ? (no over information) |
||||
###### *Does the code avoid code grouping ? |
||||
###### *Does the code have a consistent naming scheme (camelCase, under_scores) ? |
||||
###### *Does the code obey the principles "DRY" (Don't Repeat Yourself) or "DIE" (Duplication is Evil) ? |
||||
###### *Does the code obey the principal "KISS" (keep it simple, stupid) ? |
||||
###### *Does the code obey the principle YAGNI (You Aren’t Gonna Need It) ? |
||||
###### *Does the code obey the principle SOC (Separation of Concerns) |
||||
###### *Does the code avoid deep nesting (if in ifs, forest of ifs) ? |
||||
###### *Does the code present a good file and folder organization ? |
||||
###### *Does it present a good separation of Code and Data ? |
||||
###### *Does the go code follow the go recommendation ? ((https://golang.org/doc/effective_go.html), (https://golang.org/cmd/gofmt/), (https://godoc.org/golang.org/x/tools/cmd/goimports), (https://goinbigdata.com/goimports-vs-gofmt/))" |
||||
###### *Has the code passed the formatting? (gofmt, goimports) |
||||
###### *Does the project runs quickly and effectively? (Favoring recursive, no unnecessary data requests, etc) |
||||
|
||||
###### *Has the code passed the formatting ? (gofmt, goimports) |
||||
###### *Did the program runned without crashing at anytime ? |
||||
###### *Does the project runs quickly and effectively ? (Favoring of recursive, no unnecessary data requests, etc) |
||||
###### *Does the code present commenting (https://github.com/01-edu/public/blob/master/subjects/good-practices.en.md)? |
||||
###### *Does the code present documentation? |
||||
###### *Does it present consistent indentation? |
||||
###### *Does the code avoid obvious comments (no over information)? |
||||
###### *Does the code avoid code grouping? |
||||
###### *Does the code have a consistent naming scheme (camelCase, under_scores)? |
||||
###### *Does the code obey the principles "DRY" (Don't Repeat Yourself) or "DIE" (Duplication is Evil)? |
||||
###### *Does the code obey the principal "KISS" (keep it simple, stupid)? |
||||
###### *Does the code obey the principle "YAGNI" (You Are not Gonna Need It)? |
||||
###### *Does the code obey the principle "SOC" (Separation of Concerns)? |
||||
###### *Does the code avoid deep nesting (if in ifs, forest of ifs)? |
||||
###### *Does the code present a good file and folder organization? |
||||
###### *Does it present a good separation of Code and Data? |
||||
###### *Does the go code follow the go recommendation? (https://github.com/01-edu/public/blob/master/subjects/good-practices.en.md) |
||||
|
||||
###### *Is the error handled, is it error free ? |
||||
###### *Is there a test file for this code ? |
||||
###### *Are the tests checking each case ? |
||||
###### *Is the output of the program well structured? Does any letter seems to be out of scoop ? |
||||
###### *Is the error handled, is it error free? |
||||
###### *Is there a test file for this code? |
||||
###### *Are the tests checking each case possible? |
||||
###### *Is the output of the program well structured? Does any letter seems to be out of line? |
||||
|
||||
###### *Can the project be used for a common good ? |
||||
###### *Did you learn anything from this project ? |
||||
###### *Can it be open-sourced / be used for other sources ? |
||||
###### *Would you recommend/nominate this program as an example for the rest of the school ? |
||||
#### Social |
||||
|
||||
###### *Did you learn anything from this project? |
||||
###### *Can it be open-sourced / be used for other sources? |
||||
###### *Would you recommend/nominate this program as an example for the rest of the school? |
@ -1,50 +1,156 @@
|
||||
#### Functional Project Questions |
||||
|
||||
##### Try passing as arguments `"hello" standard --output=test1.txt` |
||||
##### Try passing as arguments `"First\nTest" shadow --output=test00.txt` |
||||
``` |
||||
student$ cat test00.txt |
||||
|
||||
_|_|_|_| _| _| |
||||
_| _| _|_| _|_|_| _|_|_|_| |
||||
_|_|_| _| _|_| _|_| _| |
||||
_| _| _| _|_| _| |
||||
_| _| _| _|_|_| _|_| |
||||
|
||||
|
||||
|
||||
_|_|_|_|_| _| |
||||
_| _|_| _|_|_| _|_|_|_| |
||||
_| _|_|_|_| _|_| _| |
||||
_| _| _|_| _| |
||||
_| _|_|_| _|_|_| _|_| |
||||
|
||||
|
||||
|
||||
``` |
||||
###### Does it save the right output in the right file? |
||||
##### Try passing as arguments `"123 -> !#$&%" standard --output=test2.txt` |
||||
##### Try passing as arguments `"hello" standard --output=test01.txt` |
||||
``` |
||||
student$ cat test01.txt |
||||
_ _ _ |
||||
| | | | | | |
||||
| |__ ___ | | | | ___ |
||||
| _ \ / _ \ | | | | / _ \ |
||||
| | | | | __/ | | | | | (_) | |
||||
|_| |_| \___| |_| |_| \___/ |
||||
|
||||
|
||||
|
||||
``` |
||||
###### Does it save the right output in the right file? |
||||
##### Try passing as arguments `"432 -> !#$%&@" shadow --output=test3.txt` |
||||
##### Try passing as arguments `"123 -> #$%" standard --output=test02.txt` |
||||
``` |
||||
student$ cat test02.txt |
||||
__ _ _ _ _ __ |
||||
_ ____ _____ \ \ _| || |_ | | (_) / / |
||||
/ | |___ \ |___ / ______ \ \ |_ __ _| / __) / / |
||||
| | __) | |_ \ |______| > > _| || |_ \__ \ / / |
||||
| | / __/ ___) | / / |_ __ _| ( / / / _ |
||||
|_| |_____| |____/ /_/ |_||_| |_| /_/ (_) |
||||
|
||||
|
||||
|
||||
``` |
||||
###### Does it save the right output in the right file? |
||||
##### Try passing as arguments `"432 -> #$%&@" shadow --output=test03.txt` |
||||
``` |
||||
student$ cat test03.txt |
||||
|
||||
_| _| _|_|_| _|_| _| _| _| _| _|_| _| _| _|_|_|_|_| |
||||
_| _| _| _| _| _| _|_|_|_|_| _|_|_| _|_| _| _| _| _| _| |
||||
_|_|_|_| _|_| _| _|_|_|_|_| _| _| _| _|_| _| _|_| _| _| _|_|_| _| |
||||
_| _| _| _| _|_|_|_|_| _|_| _| _|_| _| _| _| _| _| _| |
||||
_| _|_|_| _|_|_|_| _| _| _| _|_|_| _| _|_| _|_| _| _| _|_|_|_| |
||||
_| _| |
||||
_|_|_|_|_|_| |
||||
|
||||
``` |
||||
###### Does it save the right output in the right file? |
||||
##### Try passing as arguments `"There" shadow --output=test4.txt` |
||||
##### Try passing as arguments `"There" shadow --output=test04.txt` |
||||
``` |
||||
student$ cat test04.txt |
||||
|
||||
_|_|_|_|_| _| |
||||
_| _|_|_| _|_| _| _|_| _|_| |
||||
_| _| _| _|_|_|_| _|_| _|_|_|_| |
||||
_| _| _| _| _| _| |
||||
_| _| _| _|_|_| _| _|_|_| |
||||
|
||||
|
||||
|
||||
``` |
||||
###### Does it save the right output in the right file? |
||||
##### Try passing as arguments `"123 -> !"#$%@" thinkertoy --output=test5.txt` |
||||
##### Try passing as arguments `"123 -> \"#$%@" thinkertoy --output=test05.txt` |
||||
``` |
||||
student$ cat test05.txt |
||||
o o | | |
||||
0 -- o-o o | | | | -O-O- O o |
||||
/| o o | \ -O-O- o | | o / / \ |
||||
o | / oo O | | -O-O- / o O-o |
||||
| / | o-o / -O-O- | | o / o \ |
||||
o-o-o o--o o-o o | | -O-O- O o- |
||||
| | |
||||
|
||||
|
||||
``` |
||||
###### Does it save the right output in the right file? |
||||
##### Try passing as arguments `"2 you" thinkertoy --output=test6.txt` |
||||
##### Try passing as arguments `"2 you" thinkertoy --output=test06.txt` |
||||
``` |
||||
student$ cat test06.txt |
||||
|
||||
-- |
||||
o o |
||||
/ o o o-o o o |
||||
/ | | | | | | |
||||
o--o o--O o-o o--o |
||||
| |
||||
o--o |
||||
|
||||
``` |
||||
###### Does it save the right output in the right file? |
||||
##### Try passing as arguments `"Testing long output!" standard --output=test7.txt` |
||||
##### Try passing as arguments `"Testing long output!" standard --output=test07.txt` |
||||
``` |
||||
student$ cat test07.txt |
||||
_______ _ _ _ _ _ _ |
||||
|__ __| | | (_) __ _ | | __ _ | | | | | | |
||||
| | ___ ___ | |_ _ _ __ / _` | | | ___ _ __ / _` | ___ _ _ | |_ _ __ _ _ | |_ | | |
||||
| | / _ \ / __| | __| | | | '_ \ | (_| | | | / _ \ | '_ \ | (_| | / _ \ | | | | | __| | '_ \ | | | | | __| | | |
||||
| | | __/ \__ \ \ |_ | | | | | | \__, | | | | (_) | | | | | \__, | | (_) | | |_| | \ |_ | |_) | | |_| | \ |_ |_| |
||||
|_| \___| |___/ \__| |_| |_| |_| __/ | |_| \___/ |_| |_| __/ | \___/ \__,_| \__| | .__/ \__,_| \__| (_) |
||||
|___/ |___/ | | |
||||
|_| |
||||
|
||||
``` |
||||
###### Does it save the right output in the right file? |
||||
##### Try passing as arguments `"this is a long string for testing purposes!" standard --output=test8.txt` |
||||
|
||||
###### Does it save the right output in the right file? |
||||
##### Are all the test files saved? |
||||
###### Are all the test files saved? |
||||
|
||||
#### Basic |
||||
|
||||
###### *Does the code present commenting ? (https://github.com/01-edu/public/blob/master/subjects/good-practices.en.md) |
||||
###### *Does the code present documentation ? |
||||
###### *Does it present consistent indentation ? |
||||
###### *Does the code avoid obvious comments ? (no over information) |
||||
###### *Does the code avoid code grouping ? |
||||
###### *Does the code have a consistent naming scheme (camelCase, under_scores) ? |
||||
###### *Does the code obey the principles "DRY" (Don't Repeat Yourself) or "DIE" (Duplication is Evil) ? |
||||
###### *Does the code obey the principal "KISS" (keep it simple, stupid) ? |
||||
###### *Does the code obey the principle YAGNI (You Aren’t Gonna Need It) ? |
||||
###### *Does the code obey the principle SOC (Separation of Concerns) |
||||
###### *Does the code avoid deep nesting (if in ifs, forest of ifs) ? |
||||
###### *Does the code present a good file and folder organization ? |
||||
###### *Does it present a good separation of Code and Data ? |
||||
###### *Does the go code follow the go recommendation ? ((https://golang.org/doc/effective_go.html), (https://golang.org/cmd/gofmt/), (https://godoc.org/golang.org/x/tools/cmd/goimports), (https://goinbigdata.com/goimports-vs-gofmt/))" |
||||
|
||||
###### *Has the code passed the formatting ? (gofmt, goimports) |
||||
###### *Did the program runned without crashing at anytime ? |
||||
###### *Does the project runs quickly and effectively ? (Favoring of recursive, no unnecessary data requests, etc) |
||||
|
||||
###### *Is the error handled, is it error free ? |
||||
###### *Is there a test file for this code ? |
||||
###### *Are the tests checking each case ? |
||||
###### *Is the output of the program well structured? Does any letter seems to be out of scoop ? |
||||
|
||||
###### *Can the project be used for a common good ? |
||||
###### *Did you learn anything from this project ? |
||||
###### *Can it be open-sourced / be used for other sources ? |
||||
###### *Would you recommend/nominate this program as an example for the rest of the school ? |
||||
###### *Has the code passed the formatting? (gofmt, goimports) |
||||
###### *Does the project runs quickly and effectively? (Favoring recursive, no unnecessary data requests, etc) |
||||
|
||||
###### *Does the code present commenting (https://github.com/01-edu/public/blob/master/subjects/good-practices.en.md)? |
||||
###### *Does the code present documentation? |
||||
###### *Does it present consistent indentation? |
||||
###### *Does the code avoid obvious comments (no over information)? |
||||
###### *Does the code avoid code grouping? |
||||
###### *Does the code have a consistent naming scheme (camelCase, under_scores)? |
||||
###### *Does the code obey the principles "DRY" (Don't Repeat Yourself) or "DIE" (Duplication is Evil)? |
||||
###### *Does the code obey the principal "KISS" (keep it simple, stupid)? |
||||
###### *Does the code obey the principle "YAGNI" (You Are not Gonna Need It)? |
||||
###### *Does the code obey the principle "SOC" (Separation of Concerns)? |
||||
###### *Does the code avoid deep nesting (if in ifs, forest of ifs)? |
||||
###### *Does the code present a good file and folder organization? |
||||
###### *Does it present a good separation of Code and Data? |
||||
###### *Does the go code follow the go recommendation? (https://github.com/01-edu/public/blob/master/subjects/good-practices.en.md) |
||||
|
||||
###### *Is the error handled, is it error free? |
||||
###### *Is there a test file for this code? |
||||
###### *Are the tests checking each case possible? |
||||
###### *Is the output of the program well structured? Does any letter seems to be out of line? |
||||
|
||||
#### Social |
||||
|
||||
###### *Did you learn anything from this project? |
||||
###### *Can it be open-sourced / be used for other sources? |
||||
###### *Would you recommend/nominate this program as an example for the rest of the school? |
Loading…
Reference in new issue