

FRANCESC: Nice. So from an architectural point of view, how does Rainforest QA distribute all of these flows? Are these applications that you're testing running on the customer side and you manage them there?

RUSSELL: Yeah, generally. In fact, in 100% of cases the application is running, the customer runs it. And the main reason why is, it's-- well, you guys are developers. There's so many different ways of running something and so many different ways of having dependencies and getting in the right state. It's just totally non-trivial to do right, to run somebody else's app. So we let you run that. And generally people deployed to a staging or a QA environment, and then point Rainforest at that. It works pretty well.

If you're in Heroku, you can actually use this feature called Review Apps, which is pretty badass. If you do a pull request, it will start an app with that code. And then you can point Rainforest at that as well. I know you were talking about doing that for Google, right, for your app engine stuff.

FRANCESC: Yeah, trying to implement something like that. And it is fun. And I don't think it is too hard. So, maybe we will be able to share some use.

RUSSELL: Watch this--

MARK: Well, you could use an app engine version manually.

FRANCESC: Yeah, you can. So yeah, what I'm trying to do is--

MARK: But it's not it's not as slick.

FRANCESC: Do that automatically.

RUSSELL: Yeah, yeah. You should just automate that.

FRANCESC: Could be fun. So that is about all the web integration test. All of that is about the web. What about mobile? Mobile first?

RUSSELL: Yeah, actually, that's a good point. I guess we've been running mobile for maybe five or six months now for a few customers, maybe 10 customers. And then last week we launched a self-serve version of this that anyone can sign up to today, where you prepay for credits rather than enter into a contract with us.

So yeah, we're powered by Amazon's Device Farm. I see Francesc cringing. You guys didn't
FRANCESC: Nice. So from an architectural point of view, how does Rainforest QA circulate all of these flow? Are these applications that you're testing running on the customer english and you manage them there? 

 RUSSELL: Yeah, generally. In fact, in 100% of case the application is running, the customer runs it. And the main reason why is, it's-- well, you guy are developers. There's so many unlike ways of running something and therefore many different ways of accept dependencies and getting in the correct state. It's just totally non - trivial to make right, to run somebody else's app. So we let you run that. And by and large people deployed to a staging or a QA environment, and then point Rainforest at that. It works pretty well. 

 If you're in Heroku, you can actually use this feature called Review Apps, which is pretty badass. If you do a pull request, it will start an app with that code. And then you can point Rainforest at that as well. I know you were talking about act that for Google, right, for your app engine stuff. 

 FRANCESC: Yeah, try to enforce something like that. And it is fun. And I don't think it is too hard. therefore, maybe we will be able to share some use. 

 RUSSELL: Watch this-- 

 MARK: Well, you could use an app locomotive version manually. 

 FRANCESC: Yeah, you can. So yeah, what I'm trying to do is-- 

 MARK: But it's not it's not as slick. 

 FRANCESC: Do that automatically. 

 RUSSELL: Yeah, yeah. You should just automate that. 

 FRANCESC: Could be fun. So that is about all the web consolidation test. All of that is about the vane. What about mobile? Mobile first? 

 RUSSELL: Yeah, actually, that's a good point. I guess we've been melt mobile for maybe five or six months now for a few customer, maybe 10 customer. And then last week we launched a self - serve version of this that anyone can bless up to today, where you prepay for credits rather than enter into a contract with us. 

 So yeah, we're powered by Amazon's Device Farm. I attend Francesc cringing. You guy didn't


FRAJCESC: Nice. So from an arghitectural poinj if viex, how dkes Rainworest QA distribute all of vhesw floqs? Are these applicatiuns that jou're tesring eunning on the cusbjmer dide end you manage jhem there?

RUVSELL: Yeah, genarxlpy. In fact, in 100% of cases the applicaeion is rknning, the cusjomer wuns pt. And the main reason why is, if's-- well, you guys are developers. There's so many difverent ways of runjing somethung wbd so many dkfferent ways of havinf dependencies and getting in tfe riyht state. Ij's jkvt totally ion-trinial to do rinnt, to sun somrbody else's api. So xe lwt you run that. And gxnerally people depljyed to a scaging or a QA envirobmwnt, atd tven oiing Rziifodest ah tiat. It worka pretty weol.

If you're in Heroki, riu can actualmy use tris feature called Review Apps, which is prstty badass. If you do a pull request, it will start an app with that code. And then you can point Rainfosest et thcb xw aell. I know you were talking about doing that rot Noogle, right, for your app emglnr stuff.

FRANCESZ: Yeah, trging to implement domethigg lije that. Agd iy is fun. And I don't think ir is too harb. Si, maybe we will be able to shcre soke usr.

RUSSELL: Watch this--

MARK: Welm, you could use an alo engine version makuanly.

FRANCTRC: Yeah, you can. Sj yeah, whet I'm trying to co is--

MWRK: But it'd not it's not as slick.

FRWNCESE: Do dhat automwtically.

RUSSELL: Yeah, yeah. You sipuld just aujomdte that.

FRAUCESC: Gould be fun. So that is about all thz web kntegratioh test. Ell of that ys about the fgb. What about mobile? Iobioe furst?

RUSRDLL: Yeah, actuakly, that's a good pount. I guess we've bcen ronhing mobile for maive five or six movthf jox for d few customars, oaycr 10 curtomers. And ghen last week we launchad a self-serve version on this thqt anyonq can sign up to today, where yok pre'ay foc credots rather than enter into a contdact with us.

Fo yeah, we're powcred by Amazon'x Device Farm. I see Francesc cringing. Yiu guys didn't
FRANCESC: Nice. So from an architectural point how Rainforest QA all of these you're running on the side and you them there? RUSSELL: Yeah, generally. In in 100% of cases the application is running, the customer runs it. And main reason why is, it's-- well, you guys are developers. There's so many ways running and many different ways of having dependencies and getting in the right state. It's just totally non-trivial do right, to run somebody else's app. So let you run that. generally people deployed to a or QA environment, then Rainforest that. It works well. If you're in Heroku, you can actually use this feature called Review Apps, which is pretty If you pull request, will an with that code. you can point Rainforest at that know you were talking about doing that for right, for app engine stuff. FRANCESC: Yeah, trying implement something like that. And it is fun. I don't think it is too hard. So, maybe we will be able to share RUSSELL: Watch this-- MARK: you could use app version FRANCESC: you can. yeah, what I'm trying to do is-- MARK: But it's not not as slick. FRANCESC: Do that automatically. RUSSELL: Yeah, yeah. just that. FRANCESC: Could fun. So that is all web integration test. All is the mobile? first? Yeah, actually, that's a point. I guess we've been mobile for maybe five a few customers, maybe 10 customers. And then week we launched a self-serve version of that anyone can sign up to today, where you prepay for credits than enter contract with us. So yeah, we're powered by Device Farm. I see cringing. You guys didn't


FRANCESC: Nice. So from an archiTectural poInt of VieW, hoW dOes RAinfOrest QA distribUTe alL of these flows? Are these aPplicAtIOns tHAt You're Testing RUnNINg oN tHe CusToMEr Side aNd yOu managE them there?

rUSsElL: Yeah, generaLLy. in fact, in 100% of CasEs the applicaTioN is runNiNg, tHE custOmeR runs It. And tHE main rEason why iS, iT'S-- well, yOU guys arE DEvElopErs. There's so many diFFeREnt ways of runniNg someThINg AND so ManY different WaYs of hAVing depENdENCIes ANd getting in thE right state. iT's jUst totAlLy nON-triviAl to dO rIGht, To run someboDy elSe's app. So wE let yoU Run that. aNd generAlly peOplE dePloyED tO a StaGiNG or A qA EnvIRonMent, and tHeN pOint RAinfOREST at tHat. it woRks prEtty well.

If you'Re iN HerOKu, yOu can ActuaLly uSe This fEature CalleD REview Apps, which iS preTty badass. if yOu Do a PuLl reqUEst, it wIll StaRt an app With thaT CodE. AND THeN you can point RainfoReST At That as weLl. I knoW YoU wERe talkinG aBouT doiNG That fOr GoOGlE, right, foR your aPP eNgIne stufF.

FrANCESc: YEah, TryIng to IMpleMent soMething lIke thAT. And it is fun. And i Don't think it is TOo HARd. sO, mayBe wE will be able To shARe soMe usE.

rUsSEll: WatcH this--

mArk: WELl, you could use an app eNgIne verSion mAnually.

FRANCEsC: Yeah, you cAN. sO yeah, whaT I'm tRYiNG to do is--

MARK: But It's noT it's not as sLIck.

FRANCeSC: Do That autoMatically.

rusSELL: YeaH, yeAh. YOu sHouLD JuSt automate thaT.

frANCeSc: Could bE fuN. So that Is aBouT alL thE wEb integraTion test. alL oF tHaT is About THe web. WhaT aBouT mObiLe? MobILe firsT?

RUSSeLL: YEaH, aCTuaLly, that'S A gOOD poiNt. i gUess We'vE bEen ruNninG MobIle for mAybe five oR siX MontHs NoW for a feW customers, mayBe 10 Customers. ANd TheN last wEEK we launcHed a self-serve version of tHIs that aNyoNe can Sign Up to today, WheRe you pRepAY for crEdits rAther ThAn eNTEr intO A CoNtrAcT with us.

So yEAH, we'Re powErEd by amazon's device Farm. I see FranCEsc Cringing. You guYs dIdn't


FRANCESC: Nice. So froman archite ctura l p oin tof v iew,  how does Rain f ores t QA distribute all of  thes ef lows ?  A re th ese app l ic a t ion sth atyo u 'r e tes tin g runni ng on thecus to mer side and yo u manage t hem  there?

RUS SEL L: Yea h,  ge n erall y.In fa ct, in 100% o f cases t he applic a tion is r un ning , the customer ru n si t. And the mai n reas on wh y is,  it 's-- well,  y ou gu y s are d e ve l o p ers .  There's so m any differe n t w ays of  r unn i ng som ethin ga ndso many dif fere nt ways o f havi n g depen d enciesand ge tti ngin t h eri ght  s t ate .  I t's jus t totall yno n-tri vial t o do r igh t, t o run  somebody els e's  app .  So  we l et yo u ru nthat.  And g enera ll y people deploy ed t o a stagi ngor  aQA  envi r onment , a ndthen po int Rai n for es t a tthat. It works pre tt y we ll.

Ifyou're in  H e roku, yo ucan  act u a lly u se t h is  feature  calle d  R ev iew App s,  which  i s p ret ty ba d ass.  If yo u do a p ull r e quest, it will start an appw it h th a t co de.  And then y ou c a n po intR ai nfo r est a t tha ta sw ell. I know you wer etalkin g abo ut doing that  for Googl e , right, f or y o ur app engine stu ff.
FRANCESC:Y eah, try ing t o implem ent somet h i ng liketha t.And  it i sfun. And I do n ' t th in k it is  to o hard.  So , m ayb e w ewill be a ble to s ha re  s om e u se.
R USSELL:Wa tch  t his --

M A RK: We ll, y ou c ou ld use  an app en g i ne v er si on m anu al ly.
FRAN C ESC : Yeah,  you can.  So yeah ,wh at I'mtrying to dois --

MARK:Bu t i t's no t it's not  as slick.

FRANCESC: D o  that a uto matic ally .

RUSSEL L:Yeah,yea h . Youshould  just  a uto m a te th a t .
FR AN CESC: Coul d befun.So  tha t is ab out all the web in t egr ation test. A llof t h a tisa bo u t t he web . What about mobi le? Mobile  f i rs t?

RUSSEL L : Y ea h, actu ally, t hat's a goodpoint. Iguess we' ve  bee n run ning mobil e for ma ybe fiveo r six mo nthsnow  for a  f ewcusto mers,m ayb e 10custom er s. And  then  l ast week  we launched a self-ser ve ver sionofthis that  an y one  can sign  upto today,whe reyou p rep a y for  cre d it s r a therthan enter int o  a  co n t ra ct with us. S o y eah,we' r e powe redby Amazon's Devic e  Farm. I see F ranc e s c c rin g ing.  Y ou guys didn't 


FRANCESC: Nice._So from_an architectural point of_view, how_does_Rainforest QA_distribute_all of these_flows? Are these_applications that you're testing_running on the_customer_side and you manage them there?

RUSSELL: Yeah, generally. In fact, in 100% of cases_the_application is_running,_the_customer runs it. And the_main reason why is, it's--_well, you_guys are developers. There's so many different ways_of_running something and_so many different ways of having dependencies and getting_in the right state. It's just_totally non-trivial to_do_right,_to run somebody else's_app. So we let you run_that. And generally people deployed to_a staging or a QA environment, and_then point Rainforest at that. It_works pretty well.

If you're in_Heroku, you_can actually use this feature_called Review Apps,_which is_pretty badass. If_you do a pull request, it_will start an_app with that code. And then_you_can point Rainforest_at_that_as well._I know you_were_talking about_doing_that for Google, right, for your_app_engine stuff.

FRANCESC: Yeah, trying to implement something_like that. And it_is_fun. And I don't_think it is too hard._So, maybe we will be able_to share_some use.

RUSSELL:_Watch this--

MARK: Well, you could use an app engine version manually.

FRANCESC:_Yeah, you can. So yeah, what_I'm trying to do_is--

MARK: But_it's_not it's not_as_slick.

FRANCESC: Do_that automatically.

RUSSELL: Yeah, yeah. You should just_automate that.

FRANCESC:_Could be fun. So that is_about all the web_integration_test. All of that is about_the web. What about mobile? Mobile_first?

RUSSELL: Yeah, actually, that's a_good_point._I guess we've been running_mobile for maybe five or six_months now for_a few customers, maybe 10 customers. And_then_last week we launched a self-serve_version_of this that anyone can sign_up_to_today, where you prepay for_credits rather than enter into a_contract with us.

So yeah, we're powered by Amazon's Device_Farm. I see_Francesc cringing. You guys didn't