Using HearThis™, communities can record and distribute their translated Scripture for themselves.
You're in the wrong place. Head over to https://software.sil.org/hearthis .
Please see Tips for Testing Palaso Software
- Download and install Visual Studio
- Download and Install the NUnit 3 Test Adapter extension from within Visual Studio
- Run build/get-dependencies-windows.sh (e.g. from within Git Bash)
- Build the solution. This will download and install NuGet dependencies.
- Assemblies not available on the build server or via nuget can be checked in to the repo in lib/dotnet. When working on the code, the development team needs to decide if any of these assemblies should be replaced with the latest version. The same is true for the myriad nuget packages that HearThis depends on.
Note that a Release build cannot be run directly (i.e., without properly installing HearThis) -- at least on a system that has Paratext -- because of the way Paratext attempts to locate the ICU DLLs. If you need to track down a bug that is only reproducible in a Release build, run the Installer and then replace the installed EXE with a locally-built one if necessary.
- Ensure NUnit 3 Test Adapter extension is installed (see above)
- Test -> Run All Tests The "BreakIntoChunks_SpeedTest" test is CPU dependent and is safe to ignore
See the HearThis Trello Board
Each time code is checked in, an automatic build begins on our TeamCity build server, running all the unit tests. This automatic build doesn't publish a new installer, however. That kind of build is launched manually, by pressing a button on the TeamCity page. This "publish" process builds HearThis, makes an installer, rsyncs it to the distribution server, and writes out a a json file that the downloads page reads so that it can display options to the user.
Please avoid making spurious white space changes. HearThis uses tabs, not spaces, for indentation.
