Browse Source

questions for ascii-art fs, output, justify

pull/400/head
MSilva95 5 years ago
parent
commit
0e321e713e
  1. 144
      subjects/ascii-art/ascii-art-fs.audit.en.md
  2. 53
      subjects/ascii-art/ascii-art-justify.audit.en.md
  3. 50
      subjects/ascii-art/ascii-art-output.audit.en.md

144
subjects/ascii-art/ascii-art-fs.audit.en.md

@ -0,0 +1,144 @@
#### Functional Project Questions
##### Try passing as arguments `"hello" standard`
```
_ _ _
| | | | | |
| |__ ___ | | | | ___
| _ \ / _ \ | | | | / _ \
| | | | | __/ | | | | | (_) |
|_| |_| \___| |_| |_| \___/
```
###### Does it display the string in the right template as an ASCII art representation?
##### Try passing as arguments `"hello world" shadow`
```
_| _| _| _| _|
_|_|_| _|_| _| _| _|_| _| _| _| _|_| _| _|_| _| _|_|_|
_| _| _|_|_|_| _| _| _| _| _| _| _| _| _| _|_| _| _| _|
_| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _|
_| _| _|_|_| _| _| _|_| _| _| _|_| _| _| _|_|_|
```
###### Does it display the string in the right template as an ASCII art representation?
##### Try passing as arguments `"nice 2 meet you" thinkertoy`
```
-- o
o o o |
o-o o-o o-o / o-O-o o-o o-o -o- o o o-o o o
| | | | |-' / | | | |-' |-' | | | | | | |
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 display the string in the right template as an ASCII art representation?
##### Try passing as arguments `"you & me" standard`
```
___
_ _ ___ _ _ ( _ ) _ __ ___ ___
| | | | / _ \ | | | | / _ \/\ | '_ ` _ \ / _ \
| |_| | | (_) | | |_| | | (_> < | | | | | | | __/
\__, | \___/ \__,_| \___/\/ |_| |_| |_| \___|
__/ /
|___/
```
###### Does it display the string in the right template as an ASCII art representation?
##### Try passing as arguments `"123" shadow`
```
_| _|_| _|_|_|
_|_| _| _| _|
_| _| _|_|
_| _| _|
_| _|_|_|_| _|_|_|
```
###### Does it display the stirng in the right template as an ASCII art representation?
##### Try passing as arguments `"/(\")" thinkertoy`
```
o o
o / | | \
/ o o
o | |
/ o o
o \ /
```
###### Does it display the stirng in the right template as an ASCII art representation?
##### Try passing as arguments `"ABCDEFGHIJKLMNOPQRSTUVWXYZ" shadow`
```
_|_| _|_|_| _|_|_| _|_|_| _|_|_|_| _|_|_|_| _|_|_| _| _| _|_|_| _| _| _| _| _| _| _| _| _|_| _|_|_| _|_| _|_|_| _|_|_| _|_|_|_|_| _| _| _| _| _| _| _| _| _| _| _|_|_|_|_|
_| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _|_| _|_| _|_| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _|
_|_|_|_| _|_|_| _| _| _| _|_|_| _|_|_| _| _|_| _|_|_|_| _| _| _|_| _| _| _| _| _| _| _| _| _| _|_|_| _| _|_| _|_|_| _|_| _| _| _| _| _| _| _| _| _| _| _|
_| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _|_| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _|
_| _| _|_|_| _|_|_| _|_|_| _|_|_|_| _| _|_|_| _| _| _|_|_| _|_| _| _| _|_|_|_| _| _| _| _| _|_| _| _|_| _| _| _| _|_|_| _| _|_| _| _| _| _| _| _| _|_|_|_|_|
```
###### Does it display the stirng in the right template as an ASCII art representation?
##### Try passing as arguments `"\"#$%&/()*+,-./" thinkertoy`
```
o o | |
| | | | -O-O- O o / \ o | o o
-O-O- o | | o / o / o o \|/ | /
| | -O-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 display the stirng in the right template as an ASCII art representation?
##### Try passing as arguments `"It's Working" thinkertoy`
```
o
o-O-o o | 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
```
###### Does it display the stirng in the right template as an ASCII art representation?
##### Is the file system well organized?
#### 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 ?

53
subjects/ascii-art/ascii-art-justify.audit.en.md

@ -0,0 +1,53 @@
#### Functional Project Questions
##### Try passing as arguments `"left" --align=right`
###### Does it displays the expected result?
##### Try passing as arguments `"right" --align=left`
###### Does it displays the expected result?
##### Try passing as arguments `"hello" --align=center`
###### Does it displays the expected result?
##### Try passing as arguments `"1 Two 4" --align=justify`
###### Does it displays the expected result?
##### Try passing as arguments `"23/32" --align=right`
###### Does it displays the expected result?
##### Try passing as arguments `"ABCabc123" --align=right`
###### Does it displays the expected result?
##### Try passing as arguments `"!#$%&" --align=center`
###### Does it displays the expected result?
##### Try passing as arguments `"23Hello World!" --align=left`
###### Does it displays the expected result?
##### Try passing as arguments `"HELLO there HOW are YOU?!" --align=justify`
###### Does it displays the expected result?
##### Try passing as arguments `"a -> A b -> B c -> C" --align=right`
###### Does it displays the expected result?
#### 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 ?

50
subjects/ascii-art/ascii-art-output.audit.en.md

@ -0,0 +1,50 @@
#### Functional Project Questions
##### Try passing as arguments `"hello" standard --output=test1.txt`
###### Does it save the right output in the right file?
##### Try passing as arguments `"123 -> !#$&%" standard --output=test2.txt`
###### Does it save the right output in the right file?
##### Try passing as arguments `"432 -> !#$%&@" shadow --output=test3.txt`
###### Does it save the right output in the right file?
##### Try passing as arguments `"There" shadow --output=test4.txt`
###### Does it save the right output in the right file?
##### Try passing as arguments `"123 -> !"#$%@" thinkertoy --output=test5.txt`
###### Does it save the right output in the right file?
##### Try passing as arguments `"2 you" thinkertoy --output=test6.txt`
###### Does it save the right output in the right file?
##### Try passing as arguments `"Testing long output!" standard --output=test7.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?
#### 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 ?
Loading…
Cancel
Save