-
Notifications
You must be signed in to change notification settings - Fork 426
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
* Executable tutorial:Travis CI React * Demo proposal by despinoy and gdba, Docker implementation to a React project * revisions * removed unnecessary file * Final submission tutorial * Update README.md Co-authored-by: Agnes <agnesfo@kth.se> Co-authored-by: agnesforsberg <66953501+agnesforsberg@users.noreply.github.com> Co-authored-by: Khashayar Etemadi <khaes@kth.se>
- Loading branch information
1 parent
9a87ff5
commit 43b6a93
Showing
2 changed files
with
58 additions
and
20 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,20 +1,53 @@ | ||
# Executable Tutorial: React CI testing | ||
## Members | ||
Agnes Forsberg (agnesfo@kth.se) | ||
|
||
George Bassilious (gdba@kth.se) | ||
|
||
## Proposal: | ||
The tutorial will teach the user to create and connect a Travis CI with a React project, using katacoda to show how to do it. | ||
The React app will be a basic web application however there will be a focus in React tests to be incorporated to the CI server. | ||
There will also be an explanation to why testing is important to the DevOps practices and how to check the tests. | ||
|
||
|
||
The user will also get a chance to see how travis reacts to failed tests and how that affects the work in a DevOps environment. | ||
|
||
### What the user learns: | ||
* how to authorize Travis to work with their github account | ||
* how to implement Travis CI to a React project and how it works | ||
* how to write simple tests in React | ||
* how to view test results using a CI server | ||
|
||
# Executable Tutorial: React CI testing | ||
## Members | ||
Agnes Forsberg (agnesfo@kth.se) | ||
|
||
George Bassilious (gdba@kth.se) | ||
|
||
## Proposal: | ||
The tutorial will teach the user to create and connect a Travis CI with a React project, using katacoda to show how to do it. | ||
The React app will be a basic web application however there will be a focus in React tests to be incorporated to the CI server. | ||
There will also be an explanation to why testing is important to the DevOps practices and how to check the tests. | ||
|
||
|
||
## Final submission | ||
The tutorial can be found at Katacoda [**here**](https://www.katacoda.com/agnesforsberg/scenarios/travis-ci-with-react-testing). | ||
|
||
The Katacoda repo is [**here**](https://github.com/agnesforsberg/katacoda-scenarios). | ||
|
||
The tutorial application repo is [**here**](https://github.com/agnesforsberg/travis-react-tutorial). | ||
|
||
### Outline of tutorial | ||
1. Introduction to Continuous Integration | ||
|
||
2. Getting to know the simple React application | ||
|
||
3. Testing in React | ||
|
||
4. What is Travis CI and pros of using it? | ||
|
||
5. Travis CI and Github | ||
|
||
6. Travis CI server in action | ||
|
||
7. Travis CI server using React tests | ||
|
||
8. Take away | ||
|
||
### Running the tutorial | ||
The tutorial is run mostly on Katacoda, but for the last steps the user needs to fork the repo to implement the Travis CI server. A branch ready for this step is provided in the tutorial application repo. | ||
|
||
## Grading | ||
| | Yes | No | Remarkable | | ||
|---------------------------------------|-----|----|------------| | ||
|The TA can successful execute all the commands of the tutorial (mandatory) | **Yes** | No | **In the browser**| | ||
| If local execution, runs on Linux | **Yes** | No | Easy to set up and run| | ||
|The tutorial gives enough background | **Yes** | No | Comprehensive background| | ||
| The tutorial is easy to follow | **Yes** | No | Well Documented | | ||
| The tutorial is original, no such tutorial exists on the web | Yes | No | The teaching team has never heard of it| | ||
| The tutorial contains easter eggs | **Yes** | No | **Subtle and fun** | | ||
| The tutorial is successful (attracts comments and success) | Yes | No | Lively discussion| | ||
| The language is correct | **Yes** | No | **Interesting narrative**| | ||
|
||
## Easter eggs | ||
There are 2 easter eggs in the tutorial. If you can't find them and need the solution - look [**here**](./eastereggs.md) |
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 |
---|---|---|
@@ -0,0 +1,5 @@ | ||
### Easter egg 1 | ||
Look at the application and hover over the "Made by" section | ||
|
||
### Easter egg 2 | ||
At the final step there are some links to additional reading. Check the last one! |