Hot answers tagged hardware
To achieve what you want you will need a Macbook. You are not allowed under the Mac OS X EULA to run their software on a machine that is not made by Apple. ... you are granted a limited, non-transferable, non-exclusive license: ... (iii) to install, use and run up to two (2) additional copies or instances of the Apple Software within virtual ...
I'd suggest a standalone hard drive duplicator. Very easy to use - attach the two hard drives, press a button to clone from one drive to the other. Also has the advantage of not tying up a computer during the duplication process.
Does anyone have an idea of what might be a good tool for this job in particular? I've used lots of different methods in the past. But these days, I rely pretty much exclusively on Virtual Machines for this job. It's easy to set up a baseline. It's easy to restore it when needed.
Buy a MAC laptop and put VirtualBox on it. You can't run MAC OS on a PC, Apple won't license it. But you can run Windows on a MAC, so the choice of hardware is easy. VirtualBox runs on a MAC and supports Windows as a Guest OS. I don't know if you can buy a MAC that's already configured for this, but VirtualBox is reasonably easy to use.
One option might be using some file system that supports versioning (such as zfs). You can then return to earlier points in time with snapshots the same way as with virtual machines.
Maybe an alternative would be to plug in a number of physical USB audio devices and then programmatically "unplug" and "replug" them: Simulate USB unplug/replug Another alternative might be to have a number of bluetooth audio devices within range and programmatically connect/disconnect them: Programmatically connect/disconnect bluetooth headset
ISO 15288 covers the System lifecycle, while ISO 12207 covers the Software lifecycle. As of 2008, the two are "harmonized for concurrent use". For instance, 12207 can be used "either alone or in conjunction with ... 15288" In a bit more detail, what this means is that 15288 covers all aspects of developing a system, where examples of system components are ...
Based on my experience, (which will vary from person to person) that automation tends to bottleneck on CPU. This lends itself to working better on actual physical hardware than on virtual hardware. For that money I would by 13 mac minis and build a test grid. The mac mini gives you the option of running windows, mac os as well as virtualised linux, windows ...
A national standards body sent me a list of standards.. buried in there are references to: ISO/IEC 90003 "Software engineering - Guidelines for the application of ISO 9001:2000 to computer software" and ISO/IEC TR 90005 "Systems engineering - Guidelines for the application of ISO 9001 to system life cycle processes" which, at the very least, implies that ...
As far as I can tell (now that the WDK is officially released), DSF is still available as part of the Windows 7 WDK (on this page below the Win8 WDK downloads) - it's just been removed from the Windows 8 WDK. No idea why, because as far as I can tell, the driver model is the same, and DSF devices created in the Win7 WDK should work in Win8.
Travis, I'm coming into this a bit late, but here's some thoughts for you: What is the total run-time of all your tests? For instance, if you can schedule your suites to run in sequence overnight and have all your results waiting for you the next morning, you may only need one system to manage testing. What levels of IO do your tests require? Tests with ...
Only top voted, non community-wiki answers of a minimum length are eligible