Changesets can be listed by changeset number.
The Git repository is here.
- Revision:
- 373
- Log:
Initial import of Radiant 0.9.1, which is now packaged as a gem. This is an
import of the tagged 0.9.1 source checked out from GitHub, which isn't quite
the same as the gem distribution - but it doesn't seem to be available in an
archived form and the installed gem already has modifications, so this is
the closest I can get.
- Author:
- rool
- Date:
- Mon Mar 21 13:40:05 +0000 2011
- Size:
- 1374 Bytes
1 | Feature: Serving pages from front-end |
2 | In order to view the website content efficiently |
3 | a visitor |
4 | wants to load pages with caching enhancements |
5 | |
6 | Background: |
7 | Given the page cache is clear |
8 | |
9 | Scenario: Basic page rendering |
10 | When I go to the first page |
11 | Then I should get a 200 response code |
12 | And I should see "First body." |
13 | |
14 | Scenario: Rendering deeply nested page |
15 | When I go to the great-grandchild page |
16 | Then I should get a 200 response code |
17 | And I should see "Great Grandchild body." |
18 | |
19 | Scenario: Apache/lighttpd acceleration |
20 | Given I have turned on X-Sendfile headers |
21 | When I go to the first page |
22 | And I go to the first page |
23 | Then I should get an "X-Sendfile" header in the response |
24 | |
25 | Scenario: nginx acceleration |
26 | Given I have turned on X-Accel-Redirect headers |
27 | When I go to the first page |
28 | And I go to the first page |
29 | Then I should get an "X-Accel-Redirect" header in the response |
30 | |
31 | Scenario: page caching enabled |
32 | Given I have page caching on |
33 | When I go to the first page |
34 | Then I should get an "ETag" header in the response |
35 | And The "Cache-Control" header should be "public" |
36 | |
37 | Scenario: page caching disabled |
38 | Given I have page caching off |
39 | When I go to the first page |
40 | Then I should not get an "ETag" header in the response |
41 | And The "Cache-Control" header should be "private" |
42 |