Code/CFLite/CFNetwork: Difference between revisions
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
## d) set "Command" to "$(SolutionDir)build\CFTest Debug.app\Contents\Windows\CFTest Debug.exe". | ## d) set "Command" to "$(SolutionDir)build\CFTest Debug.app\Contents\Windows\CFTest Debug.exe". | ||
#Now build and run. | #Now build and run. | ||
#your job is to | #your job is to provide any required new code (and of course fix any bugs) to get the output to match the file "correct.txt" (except the bonjour services you have on your network may vary) | ||
#for cleaner output during testing, you can temporarily set 'kExtraLogging' to 0 (that way you just get pass / fail rather than full logging) | #for cleaner output during testing, you can temporarily set 'kExtraLogging' to 0 (that way you just get pass / fail rather than full logging) | ||
Revision as of 20:25, 1 August 2014
This page will document the results of the CFNetwork project on Freelancer.
To see work already completed, see the old page
CFTest Project
The latest CFNetwork test framework.
Update: Since the above was released, a bug has been fixed in CFBonjour. Please get this delta update.
How to get started
- Install Bonjour Print Services for Windows. (you do not need to run the printer wizard nor set up a printer, this is just a service that CFTest makes use of)
- download the CFTest project and put it in your development tree
- download the above delta updater, and merge it with the CFTest project
- in VS2008, Open the file "CFNetwork/CFTest/win_vs/CFTest.sln".
- In the "Solution Explorer"
- a) select "CFTest", right click it and pick "Properties"
- b) in the "Configuration:" menu, pick "All Configurations"
- c) go to "configuration properties->debugging"
- d) set "Command" to "$(SolutionDir)build\CFTest Debug.app\Contents\Windows\CFTest Debug.exe".
- Now build and run.
- your job is to provide any required new code (and of course fix any bugs) to get the output to match the file "correct.txt" (except the bonjour services you have on your network may vary)
- for cleaner output during testing, you can temporarily set 'kExtraLogging' to 0 (that way you just get pass / fail rather than full logging)