Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/justinharringa/frontend-nanodegree-feedreader
Udacity Front-End Nanodegree project - primary subject is testing
https://github.com/justinharringa/frontend-nanodegree-feedreader
Last synced: 7 days ago
JSON representation
Udacity Front-End Nanodegree project - primary subject is testing
- Host: GitHub
- URL: https://github.com/justinharringa/frontend-nanodegree-feedreader
- Owner: justinharringa
- Created: 2016-11-11T16:10:10.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2016-11-14T07:59:00.000Z (about 8 years ago)
- Last Synced: 2024-11-08T13:52:16.459Z (2 months ago)
- Language: JavaScript
- Size: 75.2 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Project Overview
In this project you are given a web-based application that reads RSS
feeds. The original developer of this application clearly saw the
value in testing, they've already included
[Jasmine](http://jasmine.github.io/) and even started writing their
first test suite! Unfortunately, they decided to move on to start
their own company and we're now left with an application with an
incomplete test suite. That's where you come in.## Running the project
Simply open up index.html in your browser to see the application run and
to see the Jasmine test results.Note: While it'd be nice to automate this I decided not to for this
quick project. If it were production code, I would most certainly add
something like [Yarn](https://yarnpkg.com/) and use it to manage
dependencies as well as run my test scripts.# How will I complete this project?
Review the Feed Reader Testing [Project Rubric](https://review.udacity.com/#!/projects/3442558598/rubric)
1. ~~Take the JavaScript Testing [course](https://www.udacity.com/course/ud549)~~
2. ~~Download the [required project assets](http://github.com/udacity/frontend-nanodegree-feedreader).~~
3. ~~Review the functionality of the application within your browser.~~
4. ~~Explore the application's HTML (**./index.html**), CSS (**./css/style.css**) and JavaScript (**./js/app.js**) to gain an understanding of how it works.~~
5. ~~Explore the Jasmine spec file in **./jasmine/spec/feedreader.js** and review the [Jasmine documentation](http://jasmine.github.io).~~
6. ~~Edit the `allFeeds` variable in **./js/app.js** to make the provided test fail and see how Jasmine visualizes this failure in your application.~~
7. ~~Return the `allFeeds` variable to a passing state.~~
8. ~~Write a test that loops through each feed in the `allFeeds` object and ensures it has a URL defined and that the URL is not empty.~~
9. ~~Write a test that loops through each feed in the `allFeeds` object and ensures it has a name defined and that the name is not empty.~~
10. ~~Write a new test suite named `"The menu"`.~~
11. ~~Write a test that ensures the menu element is hidden by default. You'll have to analyze the HTML and the CSS to determine how we're performing the hiding/showing of the menu element.~~
12. ~~Write a test that ensures the menu changes visibility when the menu icon is clicked. This test should have two expectations: does the menu display when clicked and does it hide when clicked again.~~
13. ~~Write a test suite named `"Initial Entries"`.~~
14. ~~Write a test that ensures when the `loadFeed` function is called and completes its work, there is at least a single `.entry` element within the `.feed` container.~~
15. ~~Write a test suite named `"New Feed Selection"`.~~
16. ~~Write a test that ensures when a new feed is loaded by the `loadFeed` function that the content actually changes.~~
17. ~~No test should be dependent on the results of another.~~
18. ~~Callbacks should be used to ensure that feeds are loaded before they are tested.~~
19. ~~Implement error handling for undefined variables and out-of-bound array access.~~
20. ~~When complete - all of your tests should pass.~~
21. ~~Write a README file detailing all steps required to successfully run the application. If you have added additional tests (for Udacious Test Coverage), provide documentation for what these future features are and what the tests are checking for.~~