At Apture we keep an extremely small team. Like most startups you do this for a number of reasons from keeping your burn low to maximizing efficiency. One of the hardest parts of working within a small team especially in a software company is the testing of your software. We try and roll code as often as possible at the office to not only test new features but improve performance and squash bugs. Over the last year of doing this I’ve found a few tricks I thought I’d share with the community.
1. Get Yourself VMWare Fusion or Parallels if on a Mac
A lot of startups primarily buy Macs nowadays to save on the “IT” costs of keeping other types of machines running. Personally I’m indifferent about Mac or Windows or Linux, but if you do run a Mac be sure to get an emulator so you can install Windows XP or a newer version of Windows to test compatible software.
2. Never trust IE Tester…and instead install Windows XP multiple times
People seem to swear by IETester to ensure their website or software is compatible with Internet Explorer browsers. I’m from the old school I want to see it in action with my own eyes to ensure its compatible. To do this within your emulator install multiple copies of the same install of Windows. What I mean buy that is pickup a copy of Windows XP and install it twice within your emulator. That way you can keep one on IE 6 and upgrade the other to IE 7 or IE 8. This way you do compatibility testing with the worst supported browser on the planet and a slightly improved one in IE 7 or IE 8.
3. Test the same browser on both Mac and Windows
We’ve been battling a bug where Flash videos bleed into the Apture Magic Search Bar. Oddly this does not happen in every browser in every operating system. Without testing the same product in Chrome Mac and Chrome Windows we probably wouldn’t have caught the problem before launch. Always test across Operating Systems even if the browser number is the same.
4. Run beta builds of browsers, but rename them to keep them seperate

If you distribute an extension or web product be sure to run beta builds of software. Be sure to rename them though so you can have the current public version and beta version coexisting on your machine. This ensures when the beta version of the software becomes public release your product is already compatible. This ensures you don’t get deemed incompatible in the FireFox Extensions gallery and your users remain happy
5. Load up your machine with 4 to 8 gigs of RAM
Even laptops nowadays support 8 gigs of ram. In fact you can get 8 gigs of ram off Amazon for $199 or less. Having this much ram ensures you can run multiple operating systems and browsers quickly and efficiently. When you start opening multiple tabs your machine will run out of ram very quickly. Just writing this blog post right now you will see I already have over half my RAM full. If I open up VMWare Fusion I may run out of ram causing my machine to slow down dramatically. You want to avoid this at all costs when testing.

