generated from hibbitts-design/docsify-open-multicourse-starter-kit
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
ash-teach
committed
Feb 5, 2024
1 parent
fd65157
commit eb88217
Showing
2 changed files
with
27 additions
and
24 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,29 +1,12 @@ | ||
# WEEK 5 (WEEK OF FEBRUARY 5) | ||
## LECTURE - TESTING | ||
## MID-SEMESTER WORK PERIOD | ||
|
||
### TESTING | ||
<div class="video-container-16by9"><iframe width="560" height="315" src="https://youtube.com/embed/FouNsDEVD-c"></iframe></div> | ||
**CHECK BACK SOON FOR CONTENT ON THE FOLLOWING TOPICS:** | ||
1. The best writing tools for writing code-based articles and documentation | ||
2. How to use and cite generative AI tools, such as ChatGPT | ||
3. How to write in-text citations and references (for articles and code projects) | ||
|
||
<!-- | ||
## ACTIVITIES | ||
### RESEARCH | ||
- Find a testing framework for your chosen programming language and / or chosen IDE or code editor. Find documentation related to the testing framework and read at least the basic principles. How easy is the documentation to understand? Could you use the tool right away? Try writing a simple test and deploying it? Did it work? What have you learned from this process? | ||
|
||
### REFLECT | ||
- When would testing have helped you most on past projects? Can you recall any past projects that would have benefitted from a test-first approach? What is the most important learning you will take from this week (even if you don't feel comfortable using a testing framework, what can you take from the principles of testing and use in future projects)? | ||
|
||
1. Did the development of the UI of your app proceed smoothly? Or were there unexpected challenges? | ||
2. To what degree did you do design work (possibly in other classes, like DGL 111) to support the development of your app? How helpful was this design in the process of development? | ||
3. How do you anticipate that your app code may change as you continue development? Do you anticipate that you will use any design patterns or architectural patterns? | ||
## OPTIONAL CONTENT | ||
- [Reading 3: Testing strategies (MIT OCW 6.005)](https://ocw.mit.edu/ans7870/6/6.005/s16/classes/03-testing/index.html) | ||
### So You Think You Know `window.open` - Jessica Campos | ||
If you don't know any JavaScript and haven't spent a lot of time with the [DOM](https://en.wikipedia.org/wiki/Document_Object_Model) some of what goes on here will be over your head. However! What we're most interested in here isn't the technical details, but the **experimental approach** that Jessica uses to explore code and features that she has little experience with. | ||
<div class="video-container-16by9"><iframe width="560" height="315" src="https://youtube.com/embed/cO2XNaLHvrQ"></iframe></div> | ||
--> | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,29 @@ | ||
# WEEK 6 (WEEK OF FEBRUARY 12) | ||
## MID-SEMESTER WORK PERIOD | ||
## LECTURE - TESTING | ||
|
||
Content for this week TBD based on class progress, but very likely will be primarily a work period. | ||
### TESTING | ||
<div class="video-container-16by9"><iframe width="560" height="315" src="https://youtube.com/embed/FouNsDEVD-c"></iframe></div> | ||
|
||
<!-- | ||
## ACTIVITIES | ||
### RESEARCH | ||
- Find a testing framework for your chosen programming language and / or chosen IDE or code editor. Find documentation related to the testing framework and read at least the basic principles. How easy is the documentation to understand? Could you use the tool right away? Try writing a simple test and deploying it? Did it work? What have you learned from this process? | ||
### REFLECT | ||
- When would testing have helped you most on past projects? Can you recall any past projects that would have benefitted from a test-first approach? What is the most important learning you will take from this week (even if you don't feel comfortable using a testing framework, what can you take from the principles of testing and use in future projects)? | ||
1. Did the development of the UI of your app proceed smoothly? Or were there unexpected challenges? | ||
2. To what degree did you do design work (possibly in other classes, like DGL 111) to support the development of your app? How helpful was this design in the process of development? | ||
3. How do you anticipate that your app code may change as you continue development? Do you anticipate that you will use any design patterns or architectural patterns? | ||
## OPTIONAL CONTENT | ||
- [Reading 3: Testing strategies (MIT OCW 6.005)](https://ocw.mit.edu/ans7870/6/6.005/s16/classes/03-testing/index.html) | ||
### So You Think You Know `window.open` - Jessica Campos | ||
If you don't know any JavaScript and haven't spent a lot of time with the [DOM](https://en.wikipedia.org/wiki/Document_Object_Model) some of what goes on here will be over your head. However! What we're most interested in here isn't the technical details, but the **experimental approach** that Jessica uses to explore code and features that she has little experience with. | ||
<div class="video-container-16by9"><iframe width="560" height="315" src="https://youtube.com/embed/cO2XNaLHvrQ"></iframe></div> | ||
--> | ||
|
||
|