Searched refs:mocks (Results 1 – 8 of 8) sorted by relevance
| /freebsd/contrib/ntp/sntp/unity/auto/ |
| H A D | generate_test_runner.rb | 170 def create_header(output, mocks, testfile_includes=[]) argument
172 create_runtest(output, mocks)
175 output.puts('#include "cmock.h"') unless (mocks.empty?)
183 testrunner_includes = testfile_includes - mocks
187 mocks.each do |mock|
199 def create_externs(output, tests, mocks) argument
211 def create_mock_management(output, mocks) argument
212 unless (mocks.empty?)
221 mocks.each do |mock|
229 mocks.each do |mock|
[all …]
|
| /freebsd/contrib/googletest/googlemock/ |
| H A D | README.md | 18 - Provides a declarative syntax for defining mocks.
19 - Can define partial (hybrid) mocks, which are a cross of real and mock
|
| /freebsd/contrib/googletest/docs/ |
| H A D | gmock_for_dummies.md | 11 It is easy to confuse the term *fake objects* with mock objects. Fakes and mocks
24 and code that uses it. The difference between fakes and mocks shall become much
25 clearer once you start to use mocks.
43 them fast and reliable, using mocks manually in C++ is *hard*:
45 * Someone has to implement the mocks. The job is usually tedious and
47 * The quality of those manually written mocks is a bit, uh, unpredictable. You
54 EasyMock, etc), which automate the creation of mocks. As a result, mocking is a
77 hand-written mocks.
138 If you are lucky, the mocks you need to use have already been implemented by
217 4. Exercise some code that uses the mocks; optionally, check the result using
[all …]
|
| H A D | gmock_faq.md | 91 unexpected calls on mocks without default actions don't print out a detailed
323 With gMock, you can create mocks in C++ easily. And people might be tempted to
327 When you write a test without using mocks, you exercise the code and assert that
339 case causes pain, as it's not a strong point for mocks to perform complex
340 actions. If you experience this and think that mocks suck, you are just not
390 when compiling native C++ mocks.
|
| H A D | gmock_cheat_sheet.md | 212 See [Using Mocks in Tests](gmock_for_dummies.md#using-mocks-in-tests) for more
|
| H A D | gmock_cook_book.md | 296 mocks where created using a family of macros collectively called `MOCK_METHODn`.
481 mocks, as they tend to make tests more brittle and harder to maintain. When you
487 nice mocks (not yet the default) most of the time, use naggy mocks (the current
488 default) when developing or debugging tests, and use strict mocks only as the
745 When using testing doubles (mocks, fakes, stubs, and etc), sometimes their
748 handling code) or unintentional. If your mocks have different behaviors than the
1654 For more on uninteresting calls, nice mocks, and strict mocks, read
2989 See [Using Mocks in Tests](gmock_for_dummies.md#using-mocks-in-tests) for more
3108 If you follow the following simple rules, your mocks and threads can live
3145 mess with it from multiple threads or when there still are mocks in action.
|
| H A D | faq.md | 267 of `EXPECT_DEATH()`. For example, you may want to use mocks or fake objects
|
| /freebsd/contrib/googletest/docs/reference/ |
| H A D | mocking.md | 8 GoogleTest defines the following macros for working with mocks.
410 GoogleTest defines the following classes for working with mocks.
|