Reviewers: jarin,

Message:
PTAL

Description:
Refactoring: Use explicit mock expectations for testing push and merge scripts.

- Up to now, mock expectations were simple lists of arguments + return value
- These expectations are now modeled explicitly including the name of the mock
(e.g. git or readline)
- The option test callback function is now explicitly named
- This will allow merging all mock expectations types (e.g. git and readline)
into a single list per test case (follow up CL)

TEST=tools/push-to-trunk/script_test.py

Please review this at https://codereview.chromium.org/197313002/

SVN Base: https://v8.googlecode.com/svn/branches/bleeding_edge

Affected files (+247, -222 lines):
  M tools/push-to-trunk/test_scripts.py


--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
--- You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to