ruby on rails - RSpec around() block behaves different from a before() + after() -


i'm using apartment gem manage multi-tenant rails app.

side note: if you're unfamiliar gem, switching apartments switching schema used on postgres db back-end. change apartment tenants apartment::tenant.switch!(apartment)

i have several tests test behavior under context of apartment tenant. that, use below setup (example shown controller specs)

rspec.describe mycontroller, type: :controller   before(:each)     # global before() setup   end    context "foo apartment"      ### option 1 - using around() hook     around(:each) |example|       begin         apartment::tenant.switch!("foo")         example.run       ensure         apartment::tenant.switch!("public")       end     end      ### option 2 - independent before() + after() hooks     before(:each) { apartment::tenant.switch!("foo") }     after(:each) { apartment::tenant.switch!("public") }       "tests foo apartment being used"       expect(apartment::tenant.current).to eq("foo")     end   end end

as can see, there 2 approaches setting test. 1 uses around() hook , other same thing, independently uses before() , after() hooks.

i'd imagine both approaches equivalent , interchangeable. surprisingly option 2 works.

is there reason behavior? around() block run in different order before() block?

an around(:each) block wrap before(:each) blocks (even defined @ outer scope level). because of option 1 around block you're getting following behavior

around_before   global before() setup block   example runs around_after

if global setup block sets default tenant or overwriting you're doing in around block

with option 2 get

global before() setup block before block example runs after block

Comments

Post a Comment

Popular posts from this blog

authentication - Mongodb revoke acccess to connect test database -

i have ec2 instance mongodb 3.2.0 installed. have user admin access. can connect user , perform operation remotely. 1 can connect database test remote if knows ip mongo 11.11.11.11. although not able make operations, want restrict access user credentials can connect server. first need create users , grant roles users, example: use admin db.createuser( { user: "myuseradmin", pwd: "abc123", roles: [ { role: "useradminanydatabase", db: "admin" } ] } ) then need start server --auth parameter mongod --auth more information here
Read more

r - Update two sets of radiobuttons reactively - shiny -

i have read ( how make choices in radiobuttons reactive in shiny? ) shows me how update radiobutton s in reactive way. however, when try , update 2 sets of buttons same data, 1 set renders. example: server: # create example data wafer <- rep(c(1:3), each=3) length <- c(1,1,2,1,1,1,3,5,1) width <- c(3,1,6,1,1,1,1,1,6) dd <- data.frame(wafer, length, width) shinyserver(function(input, output, session){ # create reactive dataframe store data values <- reactivevalues() values$df <- data.frame() # lengths , widths of wafer user input <- eventreactive(input$do, { subset(dd, wafer %in% input$wafer, select = length:width) }) # update reactive data frame lengths , widths have been selected user input observe({ if(!is.null(a())) { values$df <- rbind(isolate(values$df), a()) } }) output$wl <- renderdatatable({ a() }) # update radio buttons unique length , widths stored in values$df # ever "observe" put first in co...
Read more

ios - Realm over CoreData should I use NSFetchedResultController or a Dictionary? -

i'm working on app using core data , nsfetchedresultcontroller many reasons switch use realm. saw there "realm version" of nsfetchedresultcontroller on github wouldn't compatible current code using core data. the view controller displaying list of people same school, address book. list sublist of people studied in same city. so thinking make 1 unique request database retrieve list of people , filter locally list within 1 dictionary per school [string: anyobject] string section name within tableview , anyobject array of people. first solution, make nsfetchedresultcontroller each school predicate filtering location. delete actions etc.. handled delegates -> not compatible realm create dictionaries , update them each actions... -> works realm it's annoying code. any better solution? edit: i need clarify request: i'd write class inherit uitableviewcontroller. this class has list of people sorted in alphabetical order the tableview has ...
Read more