Every iOS app should be thoroughly tested in a variety of network conditions, from a high-bandwidth WiFi connection down to a data connection with a single measly bar of Edge or GPRS coverage. Finding a good connection is usually the easiest, you're almost guaranteed to have one at work or home, but reliably testing an intermittent or poor connection is much harder. The obvious way to do this is to take note of coverage dead spots as you go about your day and return to those locations to test the app, but that can be time consuming and unreliable. However, if you have Max OS X 10.7 you can simulate any network connection without even leaving your desk.

I asked myself this question straight out of college when I was being plugged into a testing role for my very first project. Fast forward about 7 years later, I still find folks confusing the two.  That's why I decided to try separating the two based on what I've been exposed to. 

You'll find various job postings, project roles and position titles fluctuating between the two. However, I believe there is a fundamental difference, especially at the level of manual testing.  The following comparisons assume a scenario by which a Tester and a Software Quality Assurance Analyst are provided with test cases already designed with test steps developed.

Consider the following scenario:  You get a flat tire while on the interstate doing 65 miles per hour, you steer the car to the side of the road and while traffic is whizzing inches by you fight to put on your spare. Now consider doing this exact same task in the comfort and safety of your driveway. You’re probably thinking ‘apples and oranges’, right?  Though the task is the exact same for each scenario, the pressures, environment and stress are on opposite ends of the spectrum.
 
Usability testing allows designers an opportunity to assess layouts, workflows, and users expected interactions with a system before sending it to the development team. This process can be fairly straight forward for users accessing the tool in a standard setting, but what about those in high pressure situations or those in highly specialized applications?
 

Testing in large scale Business Intelligence (BI) projects face challenges in data quality assurance, metrics / aggregation rules verification, source to target mapping accuracy, the test cases to the requirements traceability, and anomalies in the dimensions to facts relationships. 

Oracle Business Intelligence Enterprise Edition (OBIEE) is a BI tool that addresses quite a few of these challenges by the nature of the product's growth strategy.  As Gartner puts it, "70 functional and industry-specific packaged BI applications built on the Oracle BI Enterprise Edition Platform attests to Oracle's understanding of how to leverage the market interest in domain-specific and prepackaged solutions as a growth driver for its platform."  Customers who buy OBIEE typically also buy a relevant packaged solution.