java - How to verify if an argument passed is with correct parameters if that argument's state is changed? -


i'm trying verify object using 

@captor argumentcaptor<user> userargumentcaptor ...//define user name , jailname - var = user1 ...//call method under test. verify(userdao).getname(userargumentcaptor.capture()); verify(userdai).getjailname(userargumentcaptor.capture()); assertthat(userargumentcaptor.getallvalues()).isequalto(arrays.aslist(user1user1)); /** * notice here had use same object verify when captured in 2 different situations. */

for scenario,

user user = new user(); //object under inspection. user.setid(); //changing state here. userdao.getname(user); //capture user here. ... if(somebooleancondition) {     user.setjailstatus(true); //changing state here.     userdao.getjailname(user); //capture user here. }

while asserting userargumentcaptor.getvalue(), checking updated value. makes sense since i'm capturing object not object's state.

but, how verify object's state when passed?

i think not possible. when checking out latest version of argumentcaptor (mockito 2.7.21 @ point); there no indication @ go in direction.

the purpose respectively service offered argumentcaptor collect parameters used when method called.

what asking basically: there way additional checking @ point when call happens.

i guess, made possible: framework have allow register callback, called whenever specific method invoked on mock object. isn't possible today.

the solution see - instead of doing

@mock yourrealdaoclass themockeddao

you have do

class mockeddaoclass extends yourrealdaoclass {

and implement such things yourself. can put:

yourrealdaoclass themockeddao = new mockeddaoclass(...

into tests. other logic enable things need.

in other words: mocks generated mockito not allow enhanced testing @ point when methods invoked on mocked objects. if need (for example test like: param.getfoo().equals()) creating own stub/mock class.

what have do:

  • carefully check methods dao class has
  • decide 1 need overwrite, make sure return values need make mock work production code
  • for methods receive parameters interested in: either checking right there; or collect values later checking

Comments

Post a Comment

Popular posts from this blog

'hasOwnProperty' in javascript -

i use obj.hasownproperty judge whether object has property, when replaced obj[prop] !== undefined , not normal implementation, ask, why behind method can not use it? object.hasownproperty(prop); object[prop] !== undefined; obj[prop] !== undefined wrong 2 reasons: you can explicitly set property undefined , obj[prop] = undefined; . obj.hasownproperty(prop) return true in case. obj[prop] follow prototype chain, return property that's inherited. obj.hasownproperty(prop) returns true if property exists directly in object, returns false inherited properties.
Read more

How to understand 2 main() functions after using uftrace to profile the C++ program? -

i trying uftrace profile following simple c++ program: #include <iostream> class { public: a() {std::cout << "a created" << std::endl;} ~a() {std::cout << "a destroyed" << std::endl;} }; int main() { a; return 0; } the profile result this: # uftrace a.out created destroyed # duration tid function 2.026 [ 4828] | __cxa_atexit(); [ 4828] | main() { [ 4828] | __static_initialization_and_destruction_0() { 89.397 [ 4828] | std::ios_base::init::init(); 0.768 [ 4828] | __cxa_atexit(); 93.029 [ 4828] | } /* __static_initialization_and_destruction_0 */ 94.425 [ 4828] | } /* main */ [ 4828] | main() { [ 4828] | a::a() { 11.104 [ 4828] | std::operator <<(); 10.825 [ 4828] | std::basic_ostream::operator <<(); 24.514 [ 4828] | } /* a::a */ [ 4828] | a::~a() { 0.978 [ 4828] | ...
Read more

android - Unable to generate FCM token from dynamically instantiated Firebase -

our business logic requires instantiate firebase during runtime. fetch firebase credentials (app id, api key etc.) default firebase location after knowing user's public key , create firebase instance using credentials. this means there 2 firebase instances used within app: the default "index" firebase gives credentials second the actual firebase intend use point forward the second firebase initialised this: firebaseapp app = firebaseapp.initializeapp(<context>, <options>, <app_label>); our problem traditional method of retrieving fcm token using firebaseinstanceidservice , ontokenrefresh() fails since ontokenrefresh() method called first firebase instance. directly calling string token = firebaseinstanceid.getinstance(app).gettoken(); returns null never ready when called. have tried polling test if token generated @ point. no luck. how can generate fcm token reliably firebase instance instantiated during runtime? i...
Read more