Lux, as I understand it, tests that a property has a particular value after a custom action has run.
As far as a robust test, this is pretty weak. Setting a property is just a small part of the install process. But the sum total of an installation is to put files on the system, configure the registry, install and start services, etc. I would say, throw away Lux. Let's, as a WiX community, move beyond it. Instead, let's look into tools like TestKitchen, Vagrant, Chef and ServerSpec (especially ServerSpec). http://serverspec.org/resource_types.html The testing flow would go something like: 1. Spin up a new virtual machine (automated with Vagrant) 2. Install the MSI package (using Chef or something similar) 3. Call your acceptance tests with ServerSpec, which would have tests such as: does this file exist after installation? Does this XML file contain some expected string? Did a service get installed and is it running? 4. Tests pass, destroy VM -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-Lux-and-Nit-tp7597183p7599163.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
