@@ -70,39 +70,33 @@ Now browse to the app at `http://localhost:8000/app/index.html`.
7070
7171## Directory Layout
7272
73- app/ --> all of the files to be used in production
74- assets/ --> all static asset files
75- css/ --> css files
76- app.css --> default stylesheet
77- img/ --> image files
78- components/ --> all app specific modules
79- directives/ --> application level directives
80- appVersion.js --> custom directive that returns the current app version
81- filters/ --> application level filters
82- interpolate.js --> custom interpolation filter
83- services/ --> application level services
84- appVersionService.js --> custom service that returns the current app version
85- view1/ --> a custom module for this application
86- view1.html --> the template rendered for this module
87- view1.js --> the application logic for this module
88- view2/ --> a custom module for this application
89- view2.html --> the template rendered for this module
90- view2.js --> the application logic for this module
91- app.js --> application
92- index.html --> app layout file (the main html template file of the app)
93- index-async.html --> just like index.html, but loads js files asynchronously
94- test/ --> test config and source files
95- protractor-conf.js --> config file for running e2e tests with Protractor
96- e2e/ --> end-to-end specs
97- scenarios.js
98- karma.conf.js --> config file for running unit tests with Karma
99- unit/ --> unit level specs/tests
100- directivessSpec.js --> specs for application level directives
101- filtersSpec.js --> specs for application level filters
102- servicesSpec.js --> specs for application level services
103- view1Spec.js --> specs for the view1 module
104- view2Spec.js --> specs for the view2 module
105-
73+ ```
74+ app/ --> all of the source files for the application
75+ app.css --> default stylesheet
76+ components/ --> all app specific modules
77+ version/ --> version related components
78+ version.js --> version module declaration and basic "version" value service
79+ version_test.js --> "version" value service tests
80+ version-directive.js --> custom directive that returns the current app version
81+ version-directive_test.js --> version directive tests
82+ interpolate-filter.js --> custom interpolation filter
83+ interpolate-filter_test.js --> interpolate filter tests
84+ view1/ --> the view1 view template and logic
85+ view1.html --> the partial template
86+ view1.js --> the controller logic
87+ view1_test.js --> tests of the controller
88+ view2/ --> the view2 view template and logic
89+ view2.html --> the partial template
90+ view2.js --> the controller logic
91+ view2_test.js --> tests of the controller
92+ app.js --> main application module
93+ index.html --> app layout file (the main html template file of the app)
94+ index-async.html --> just like index.html, but loads js files asynchronously
95+ karma.conf.js --> config file for running unit tests with Karma
96+ e2e-tests/ --> end-to-end tests
97+ protractor-conf.js --> Protractor config file
98+ scenarios.js --> end-to-end scenarios to be run by Protractor
99+ ```
106100
107101## Testing
108102
@@ -114,8 +108,8 @@ The angular-seed app comes preconfigured with unit tests. These are written in
114108[ Jasmine] [ jasmine ] , which we run with the [ Karma Test Runner] [ karma ] . We provide a Karma
115109configuration file to run them.
116110
117- * the configuration is found at ` test/ karma.conf.js`
118- * the unit tests are found in ` test/unit/ ` .
111+ * the configuration is found at ` karma.conf.js `
112+ * the unit tests are found in next to the code they are testing and are named as ` ..._test.js ` .
119113
120114The easiest way to run the unit tests is to use the supplied npm script:
121115
@@ -143,8 +137,8 @@ The angular-seed app comes with end-to-end tests, again written in [Jasmine][jas
143137are run with the [ Protractor] [ protractor ] End-to-End test runner. It uses native events and has
144138special features for Angular applications.
145139
146- * the configuration is found at ` test /protractor-conf.js`
147- * the end-to-end tests are found in ` test/ e2e/ `
140+ * the configuration is found at ` e2e-tests /protractor-conf.js`
141+ * the end-to-end tests are found in ` e2e-tests/scenarios.js `
148142
149143Protractor simulates interaction with our web app and verifies that the application responds
150144correctly. Therefore, our web server needs to be serving up the application, so that Protractor
@@ -235,7 +229,7 @@ Then you can start your own development web server to serve static files from a
235229running:
236230
237231```
238- http-server
232+ http-server -a localhost -p 8000
239233```
240234
241235Alternatively, you can choose to configure your own webserver, such as apache or nginx. Just
0 commit comments