Guest post by: Barnabas Birmacher
Distributing your apps through TestFairy is great as always! Reaching your testers instantly and gathering valuable feedback and usage information is the best way to make awesome applications.
To make sure you keep deploying quality products you should use Continuous Integration and Delivery.
Continuous Integration is a practice where you push all your app’s code changes into a shared repository multiple times a day. Each integration should be verified by an automatic build, so you are going to be notified early about the problems and you can locate them quickly. Continuous Delivery works well with Continuous Integration – it means that you deploy every build to production every time a build passes the automated tests.
Working with unit tests and multiple daily deployments can give you a huge benefit but dealing with it manually also takes up a lot of time. Soon you will realise you are doing a lot more administrative tasks besides the actual development.
We, at Bitrise, are on a mission to bring back the joy of app development by automating all of these processes for you. We’ve also integrated TestFairy into Bitrise so every time you update your code we’ll deploy your app automatically to your favorite deployment service.
How to get started?
After you have connected your application to Bitrise you can change your own workflow on your application page and start customising it for your own needs.
To be able to deploy your application you are going to need an Xcode Archive step (that should be already added to your workflow).
To deploy your app to TestFairy, simply add a new TestFairy step after Xcode Archive and after every successful build we are going to deploy your application automatically.
(click image for full size)
The only required parameter you have to add is your TestFairy API Key. To get it you should navigate to your account preferences on TestFairy and find the key under the API Key menu.
You can also enable or disable the email notifications and set the tester groups you would like to notify. There’s an option to make your users upgrade to the latest build by enabling Auto update in the step. You can also start recording video and set the length of it.
We have more than 20 different integrations you can choose from. Update your build workflow by adding connections with different services like Slack or HipChat to notify your team about broken builds or successful deployments.
And that is all! Just work on your awesome app and we’ll make sure it deploys to TestFairy every time you update your code!
The Bitrise Team
Guest post by Tessa Kayser, business development manager at mNectar, a mobile app virtualization platform.
Last month, Burstly was acquired by Apple and it was announced that TestFlight would no longer support Android apps starting March 21st, 2014. Thankfully, our friends at TestFairy have an easy way for the Android developers to migrate their testing service without making any code changes.
Today, Burstly sent out a legal notice informing current clients that the SkyRocket mediation platform will be shut down in 90 days. This announcement probably leaves many developers wondering what mediation alternatives are out there.
For any developers who are looking at the current ad mediation options out there, Here are some things to consider:
Independence and Transparency
The owner of any mediation layer is a very important factor to consider. If the company is more focused on another product such as real-time bidding, support for the ad mediation side may be very limited. If the company is also an ad network, you run the risk of biased ad selection. It’s also important to have a clear explanation of how traffic will be allocated and to have optional manual control.
The main objective of using a mediation layer is to manage all of your ad networks under one interface. If only a few networks are fully supported, the product is less valuable.
Knowing that the mediation layer’s reporting matches your networks’ reporting in a clear and concise way is essential. If you are using an automatic optimization feature and the reporting is inaccurate, your revenue can suffer. It is also becomes difficult to make prioritization decisions when the reporting is unclear, slow, or wrong.
Mediation layers are complicated and problems will arise. Active support forums, responsive account managers, and helpful tech teams are all great resources that will keep things running smoothly.
An open source mediation project owned by the developer community would be ideal, but that doesn’t seem like an immediate option. We have been discussing the idea with several partners and the initial interest looks promising.
If you would like to learn more about the project or become a part of the conversation, feel free to send an email to Tessa at email@example.com.