If you'll forgive the self-promotion, you might like to check out my web app, Testpad (https://ontestpad.com), as a lightweight tool for organising manual testing. It's basically structured checklists rather than formal test case management, and has been doing well at agencies both big and small. Because it's lightweight and flexible (think cross between Excel, Notepad and OmniOutliner) you can start out as simple as you like and iterate the complexity as and when it's appropriate.
And to answer your question: I am of course using it to test itself! Plus some selenium for basic automation, but without going overboard as the app is very javascript-heavy and interactive, which limits how much can be usefully/cost-effectively achieved with automation.
FastSpring's price is ALL IN. It includes the merchant account, payment gateway and subscription features, and no setup fees nor monthly charges; just the per-transaction costs as noodle commented.
Plus, sign-up and testing is totally free and still gets awesome customer support; you only start paying them anything when you start selling your service. This struck me as ideal for an SMB in its first year.
Great to hear it worked for you. But in my case if I'm selling 3k per month with $5-10 per user, one option would charge me around $270 and other around $500. Not really good for micro payment based products.
And this isn't about SaaSy. It's same with all services out there.
Didn't find them when I went looking, that's all. FWIW, FastSpring's checkout is also a redirect, but they give you some pretty flexible control over the markup and CSS so its quite simple to keep the branding consistent.
This isn't necessary. It's an environment variable Xcode adds while running the executable, not something that is compiled into the application. Furthermore it only works in the simulator, not on the device itself, so end users wouldn't run into problems with it anyway.
Well, I suppose it's true -- I have submitted apps to Apple that got approved that leaked memory. But the leaks were coming from one of their frameworks (WebKit).
So perhaps what I said should be amended to say: "Your app does not leak memory, at least because of any code you wrote".
It's a worthy goal, but missing it still doesn't cause rejection. BTW, I do include "don't leak memory" in my general-purpose template for testing (as opposed to submitting) iOS apps here: https://ontestpad.com/library/200/ios-app-testing-template
And to answer your question: I am of course using it to test itself! Plus some selenium for basic automation, but without going overboard as the app is very javascript-heavy and interactive, which limits how much can be usefully/cost-effectively achieved with automation.