-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running tests index.cfm file #115
Comments
Can you share your code so that we can see how you are calling cfstatic? |
Dean: Thank you for responding! It is the files in the test directory, unchanged. Index.cfm and application.cfc, which then call other files. Do you want to see this code or do you have it? |
Eric, I just downloaded the latest release (0.7.2) and ran the test suite. I too am seeing some failures, but not all the ones that you are seeing. The ones that I see are: t27_cfstatic_shouldThrowError_whenOutputFolderDoesNotExistAndCannotBeCreated Failed I'm not sure how up to date the tests are, so I will have to look into it. I am running 0.7.2 on a number of sites without issue, so I don't think that you will have a problem, but we'll work on getting all the tests passing. |
Dean: Thank you for your help. Yes, I just checked that i have the 0.7.2 version. Eric On 5/14/2015 3:08 PM, Dean Lawrence wrote:
Boulder Outdoor Center, Inc. |
On my testing server I have copied the cfstatic information into my working directory:
When running cfstatic/tests/index.cfm for the first time I get these errors/fails:
t19_renderIncludes_shouldRenderJsVariablesBeforeJsIncludes_whenIncludeDataUsed Failed
t20_renderIncludes_shouldUseConfiguredCharset Failed
t27_cfstatic_shouldThrowError_whenOutputFolderDoesNotExistAndCannotBeCreated Failed
t28_renderIncludes_shouldRenderConfiguredJsVar_forRenderingData Failed
t37_cfstatic_shouldNotDeleteAllFiles_whenInCheckForUpdatesMode Failed
t39_cfstatic_shouldRebuildSourceFiles_whenChangesToDependencyFilesAreDetected Error
Is this normal or is there something I am missing?
The text was updated successfully, but these errors were encountered: