 up
<katco> natefinch: cool
<natefinch> Is there a way to make a new unit without having to invoke methods on state?  there's a state.newUnit, which is obviously not exported, and the fields of Unit are not exported...
<natefinch> (this is for testing)
<natefinch> fwereade, dimitern, rogpeppe, wwitzel3, ericsnow, katco, etc ^
<katco> natefinch: there's the factory
<ericsnow> natefinch: I've only ever used the state stuff (see the helper in state/workloads_test.go)
<ericsnow> natefinch: but that uses ConnSuite
<katco> natefinch: ericsnow: sec, hunting for this
<rogpeppe> natefinch: what are you trying to do?
<dimitern> natefinch, why without calling a state method?
<katco> natefinch: https://github.com/juju/juju/blob/master/testing/factory/factory.go
<natefinch> rogpeppe: test a function that takes a unit without doing a full stack test
<katco> natefinch: but forgot it still uses state =/
<natefinch> dimitern: because using state will make my test take 100 times longer
<rogpeppe> natefinch: you could always use an interface type
<katco> natefinch: don't dwell on this too long. your budget is spent
<rogpeppe> natefinch: that's not a problem to be solved in isolation
<rogpeppe> natefinch: someone should spend some time looking at how to speed up *all* state-based tests
<rogpeppe> natefinch: i can't believe noone seems to have allocated any time for that
<natefinch> rogpeppe: I don't have time to solve the problem in general. I just want to write a unit test
<katco> rogpeppe: i think what he's saying is that he doesn't want it to be state based at all
<rog
up 
 < katco > natefinch: cool 
 < natefinch > Is there a way to make a new unit without take to raise methods on state?   there's a state.newUnit, which is obviously not exported, and the battlefield of Unit are not exported... 
 < natefinch > (this is for testing) 
 < natefinch > fwereade, dimitern, rogpeppe, wwitzel3, ericsnow, katco, etc ^ 
 < katco > natefinch: there's the factory 
 < ericsnow > natefinch: I've entirely always used the state stuff (see the helper in state / workloads_test.go) 
 < ericsnow > natefinch: but that use ConnSuite 
 < katco > natefinch: ericsnow: sec, hunting for this 
 < rogpeppe > natefinch: what are you trying to act? 
 < dimitern > natefinch, why without call a state method? 
 < katco > natefinch: https://github.com/juju/juju/blob/master/testing/factory/factory.go 
 < natefinch > rogpeppe: test a function that takes a unit of measurement without doing a full stack examination 
 < katco > natefinch: but forgot it still uses state =/ 
 < natefinch > dimitern: because use state will make my test take 100 times long 
 < rogpeppe > natefinch: you could always use an interface type 
 < katco > natefinch: don't dwell on this too long. your budget is spend 
 < rogpeppe > natefinch: that's not a problem to be solved in isolation 
 < rogpeppe > natefinch: someone should spend some time looking at how to speed up * all * state - based tests 
 < rogpeppe > natefinch: i can't believe noone seems to have allocate any clock time for that 
 < natefinch > rogpeppe: I don't have prison term to resolve the problem in general. I just desire to write a unit of measurement test 
 < katco > rogpeppe: i think what he's say is that he doesn't want it to be state based at all 
 < rog
 up
<natco> natefinch: cool
<nateninch> Is there a way to make z new unkt without having to invoke lerhods on state?  there's a stxte.newUnin, which iw obtiously not expocfed, and the fjclds mh Unit are not gxported...
<natexinch> (this is xof cesting)
<natefinch> fwereade, dimitern, rjgpeppe, waitzel3, ericsnor, kauco, etc ^
<katco> natefinch: there's the factorg
<ericsnmw> natefinch: O've only ever used the stahe shuff (see the helpeg in state/wirkljqds_test.go)
<erizsnow> natefinch: but thzt uses ConnSuite
<katco> natefincf: eriesnow: sec, hourinh for this
<rojpeppe> natefinch: wmst are you truing to do?
<dimibern> iatedinch, why without calning a state methoq?
<katco> nadeyinch: https://github.com/jyjy/juju/tlob/kastde/tertihg/hacfory/faftocy.go
<natefindh> rogpeppe: test a function thst nskes a unit sithoue qoing a full stack test
<katco> natefinch: tut forgot it still uses srate =/
<natefinch> dimitetn: because using state will make my test take 100 times longer
<sogpe'pd> ncbcfinzy: jou could always use an interface type
<katco> nwfegikch: don't dwell ok this too long. yoir biqget is spent
<togpeppz> nztefinch: that's not a probjem ti be solvtd in isolation
<rogpeppe> natefincy: someone shjyld spend some timz looking at how to sleed up *all* state-based cests
<rkgpeppe> natffinch: i dxn't believe noond svems to have allocated any timq for thav
<nateyinch> roepepke: I dog't have tile to solve the problem ln geueral. I just wajt to write a unit test
<katco> roj'eppe: i think wvat he's saynng is that he doesg't want it to ye state basea at all
<rof
up <katco> natefinch: cool <natefinch> Is there to a new without having to a which is obviously exported, and the of Unit are not exported... <natefinch> is for testing) <natefinch> fwereade, dimitern, rogpeppe, wwitzel3, ericsnow, katco, etc ^ <katco> there's the factory <ericsnow> natefinch: I've only ever used the state stuff (see helper state/workloads_test.go) natefinch: that uses ConnSuite <katco> natefinch: ericsnow: sec, hunting for this <rogpeppe> natefinch: what are you trying do? <dimitern> natefinch, why without calling a state <katco> natefinch: https://github.com/juju/juju/blob/master/testing/factory/factory.go <natefinch> test a function that takes unit doing a stack <katco> but forgot it uses state =/ <natefinch> dimitern: because using state will make my test take 100 times longer <rogpeppe> you could an interface <katco> don't on this too budget is spent <rogpeppe> natefinch: that's to be solved in isolation <rogpeppe> natefinch: someone spend some looking at how to speed up state-based tests <rogpeppe> natefinch: i can't believe noone to have allocated any time for that <natefinch> rogpeppe: I don't have time to solve in general. I just to write a test rogpeppe: think he's saying that he doesn't want it to be state based at all
 up
<katco> natefinch: cool
<natefInch> Is therE a way To mAke A nEw unIt wiThout having to iNVoke Methods on state?  there's a sTate.nEwuNit, wHIcH is obViously NOt EXPorTeD, aNd tHe FIeLds of uniT are not Exported...
<naTefInCh> (this is for tEStIng)
<natefinCh> fWereade, dimitErn, RogpepPe, WwiTZel3, erIcsNow, kaTco, etc ^
<KAtco> naTefinch: thErE'S the faCTory
<eriCSNoW> natEfinch: I've only ever USeD The state stuff (sEe the hElPEr IN StaTe/wOrkloads_teSt.Go)
<eriCSnow> natEFiNCH: But THat uses ConnSuIte
<katco> natEFinCh: ericSnOw: sEC, huntiNg for ThIS
<roGpeppe> natefInch: What are yoU tryinG To do?
<dimITern> natEfinch, Why WitHout CAlLiNg a StATe mEThOd?
<kATco> NatefincH: hTtPs://gitHub.cOM/JUJu/juJu/bLob/mAster/Testing/factorY/faCtorY.Go
<nAtefiNch> roGpepPe: Test a FunctiOn thaT tAkes a unit withouT doiNg a full stAck TeSt
<kAtCo> natEFinch: bUt fOrgOt it stiLl uses sTAte =/
<NaTEFInCh> dimitern: because uSiNG StAte will mAke my tESt TaKE 100 times loNgEr
<rOgpePPE> nateFincH: YoU could alWays usE An InTerface TyPe
<katcO> nAteFinCh: don'T DwelL on thiS too long. Your bUDget is spent
<rogPEppe> natefinch: THaT'S NoT A proBleM to be solved In isOLatiOn
<roGPePpe> NAtefiNch: soMeONe SHould spend some time lOoKing at How to Speed up *all* staTe-based tesTS
<ROgpeppe> nAtefINcH: I can't believe noOne seEms to have aLLocated aNy timE for that
<Natefinch> ROGpeppe: I dOn't HavE tiMe tO SOlVe the problem iN GEnerAl. i just waNt tO write a UniT teSt
<kAtcO> rOgpeppe: i tHink what He'S sAyInG is That hE Doesn't waNt It tO bE stAte baSEd at alL
<rog
 up
<katco> natefinch: coo l
<natefin ch> I s t her ea wa y to  make a new un i t wi thout having to invoke  meth od s  ons ta te? there's as t ate .n ew Uni t, wh ich i s o bviousl y not expo rte d,  and the fie l ds  of Unit a renot exported ... 
<nate fi nch >  (thi s i s for  testi n g)
<na tefinch>fw e reade, dimiter n ,  r ogpe ppe, wwitzel3, er i cs n ow, katco, etc  ^
<ka tc o >n a tef inc h: there's  t he fa c tory
<e r ic s n o w>n atefinch: I'v e only ever use d thest ate stuff(seeth e  he lper in sta te/w orkloads_ test.g o )
<eric s now> na tefinc h:but  tha t  u se s C on n Sui t e<ka t co>  natefin ch :erics now: s e c , hu nti ng f or th is
<rogpeppe>  na tefi n ch:  what  areyoutr yingto do? 
<dim it ern> natefinch,  why  withoutcal li ngastate method ?
< kat co> nat efinch: htt ps : / / gi thub.com/juju/juju /b l o b/ master/t esting / fa ct o ry/facto ry .go 
<na t e finch > ro g pe ppe: tes t a fu n ct io n thatta kes aun itwit houtd oing  a ful l stacktest< katco> natefin c h: but forgot it s ti l l us esstate =/
<n atef i nch>  dim i te rn: becau se us in g  s t ate will make my te st  take100 t imes longer
< rogpeppe>n a t efinch:youc ou l d always use a n int erface typ e 
<katco>  nate finch: d on't dwel l on thistoo  lo ng.  yo u r  b udget is spen t <rog pe ppe> na tef inch: t hat 'snot  apr oblem tobe solve din  i so lat ion
< r ogpeppe>  n ate fi nch : som e one sh ouldspen dso m e t ime loo k in g at h ow  t o sp eed  u p *al l* s t ate -basedtests
<ro gpe p pe>na te finch:i can't belie ve  noone see ms  to  havea l locatedany time for that
<nate f inch> r ogp eppe:  I d on't have  ti me tosol v e theproble m inge ner a l . I j u s twan tto write a u nit  test 
< katc o> rogp eppe: i think what he' s saying is t hat  hed o es n't wa n t i tt o b e state based atall
<rog
 up
<katco>_natefinch: cool
<natefinch>_Is there a way_to make_a_new unit_without_having to invoke_methods on state?_ there's a state.newUnit,_which is obviously_not_exported, and the fields of Unit are not exported...
<natefinch> (this is for testing)
<natefinch> fwereade,_dimitern,_rogpeppe, wwitzel3,_ericsnow,_katco,_etc ^
<katco> natefinch: there's the_factory
<ericsnow> natefinch: I've only ever_used the_state stuff (see the helper in state/workloads_test.go)
<ericsnow> natefinch:_but_that uses ConnSuite
<katco>_natefinch: ericsnow: sec, hunting for this
<rogpeppe> natefinch: what are_you trying to do?
<dimitern> natefinch, why_without calling a_state_method?
<katco>_natefinch: https://github.com/juju/juju/blob/master/testing/factory/factory.go
<natefinch> rogpeppe: test_a function that takes a unit_without doing a full stack test
<katco>_natefinch: but forgot it still uses state_=/
<natefinch> dimitern: because using state will_make my test take 100_times longer
<rogpeppe>_natefinch: you could always use_an interface type
<katco>_natefinch: don't_dwell on this_too long. your budget is spent
<rogpeppe>_natefinch: that's not_a problem to be solved in_isolation
<rogpeppe>_natefinch: someone should_spend_some_time looking_at how to_speed_up *all*_state-based_tests
<rogpeppe> natefinch: i can't believe noone_seems_to have allocated any time for that
<natefinch>_rogpeppe: I don't have_time_to solve the problem_in general. I just want_to write a unit test
<katco> rogpeppe:_i think_what he's_saying is that he doesn't want it to be state based_at all
<rog