Is there a way to fake a method response using Mock or Stubs? Announcing the arrival of Valued...
What's parked in Mil Moscow helicopter plant?
All ASCII characters with a given bit count
VBA: Single line if statement with multiple actions
Cisco DHCP Router
When I export an AI 300x60 art board it saves with bigger dimensions
What is the ongoing value of the Kanban board to the developers as opposed to management
TV series episode where humans nuke aliens before decrypting their message that states they come in peace
Was Objective-C really a hinderance to Apple software development?
What do you call an IPA symbol that lacks a name (e.g. ɲ)?
What is the definining line between a helicopter and a drone a person can ride in?
How can I wire a 9-position switch so that each position turns on one more LED than the one before?
Translate text contents of an existing file from lower to upper case and copy to a new file
Not within Jobscope - Aggravated injury
What is ls Largest Number Formed by only moving two sticks in 508?
Did war bonds have better investment alternatives during WWII?
How did Elite on the NES work?
Processing ADC conversion result: DMA vs Processor Registers
Why do owned slices take 16 bytes in rust? (on x64 machine)
Does Prince Arnaud cause someone holding the Princess to lose?
Suing a Police Officer Instead of the Police Department
Does using the Inspiration rules for character defects encourage My Guy Syndrome?
Why doesn't the university give past final exams' answers?
How was Lagrange appointed professor of mathematics so early?
Show two Lagrangians are equivalent
Is there a way to fake a method response using Mock or Stubs?
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
2019 Community Moderator Election ResultsDoes HttpCalloutMock work when the tested method doesn't return HttpResponse?Mock class not working with Dynamic & Unique end-pointHTTP Mock Response class has 0 coverageIs there a way to create more than 50000 records in a unit test context?Mock Service .setBody()Post callout behavior assertions for unit test with static resource callout mock failBasic Mock Test Coverage HelpHow can I reference a trigger's method and/or variable from a test class?Can we mock relationships in Apex?Method Is Not Visible: APEX Trailhead Unit Testing Challenge
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I have a helper method in my code called canQueryObject, and that method returns a boolean. I have some code that calls the method via the following line of code:
if(!myObjectHelper.canQueryObject(Schema.SObjectType.<<objectType>>)){ ... }
I'd like to test some scenarios where the scenario is false. Is there a way I can use Mock or Stubs in a unit-test to set canQueryObject to false?
unit-test mock
add a comment |
I have a helper method in my code called canQueryObject, and that method returns a boolean. I have some code that calls the method via the following line of code:
if(!myObjectHelper.canQueryObject(Schema.SObjectType.<<objectType>>)){ ... }
I'd like to test some scenarios where the scenario is false. Is there a way I can use Mock or Stubs in a unit-test to set canQueryObject to false?
unit-test mock
add a comment |
I have a helper method in my code called canQueryObject, and that method returns a boolean. I have some code that calls the method via the following line of code:
if(!myObjectHelper.canQueryObject(Schema.SObjectType.<<objectType>>)){ ... }
I'd like to test some scenarios where the scenario is false. Is there a way I can use Mock or Stubs in a unit-test to set canQueryObject to false?
unit-test mock
I have a helper method in my code called canQueryObject, and that method returns a boolean. I have some code that calls the method via the following line of code:
if(!myObjectHelper.canQueryObject(Schema.SObjectType.<<objectType>>)){ ... }
I'd like to test some scenarios where the scenario is false. Is there a way I can use Mock or Stubs in a unit-test to set canQueryObject to false?
unit-test mock
unit-test mock
edited 1 hour ago
WEFX
asked 1 hour ago
WEFXWEFX
1538
1538
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I typically use a fairly simple pattern and don't bring in a framework. It would look something like the following:
public virtual with sharing class MyObjectHelper
{
static MyObjectHelper instance = new MyObjectHelper();
@TestVisible static void setMock(MyObjectHelper mock) { instance = mock; }
public static Boolean canQueryObject(SObjectType sObjectType)
{
return instance.getCanQueryObject(sObjectType);
}
// the two method names cannot match or you will get a compile fail
protected virtual Boolean getCanQueryObject(SObjectType sObjectType)
{
return sObjectType.getDescribe().isQueryable();
}
}
Then in your test, you can have a mock return always true or always false, as you wish.
@IsTest
class MyObjectHelperTests
{
class HelperMock extends MyObjectHelper
{
Boolean isQueryable = true;
protected override Boolean getCanQueryObject(SObjectType sObjectType)
{
return isQueryable;
}
}
@IsTest static void testCannotQuery()
{
HelperMock mock = new HelperMock();
mock.isQueryable = false;
MyObjectHelper.setMock(mock);
Test.startTest();
Boolean canQuery = MyObjectHelper.canQueryObject(...);
Test.stopTest();
system.assertEquals(false, canQuery, 'Some informative message');
}
}
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "459"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f258841%2fis-there-a-way-to-fake-a-method-response-using-mock-or-stubs%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I typically use a fairly simple pattern and don't bring in a framework. It would look something like the following:
public virtual with sharing class MyObjectHelper
{
static MyObjectHelper instance = new MyObjectHelper();
@TestVisible static void setMock(MyObjectHelper mock) { instance = mock; }
public static Boolean canQueryObject(SObjectType sObjectType)
{
return instance.getCanQueryObject(sObjectType);
}
// the two method names cannot match or you will get a compile fail
protected virtual Boolean getCanQueryObject(SObjectType sObjectType)
{
return sObjectType.getDescribe().isQueryable();
}
}
Then in your test, you can have a mock return always true or always false, as you wish.
@IsTest
class MyObjectHelperTests
{
class HelperMock extends MyObjectHelper
{
Boolean isQueryable = true;
protected override Boolean getCanQueryObject(SObjectType sObjectType)
{
return isQueryable;
}
}
@IsTest static void testCannotQuery()
{
HelperMock mock = new HelperMock();
mock.isQueryable = false;
MyObjectHelper.setMock(mock);
Test.startTest();
Boolean canQuery = MyObjectHelper.canQueryObject(...);
Test.stopTest();
system.assertEquals(false, canQuery, 'Some informative message');
}
}
add a comment |
I typically use a fairly simple pattern and don't bring in a framework. It would look something like the following:
public virtual with sharing class MyObjectHelper
{
static MyObjectHelper instance = new MyObjectHelper();
@TestVisible static void setMock(MyObjectHelper mock) { instance = mock; }
public static Boolean canQueryObject(SObjectType sObjectType)
{
return instance.getCanQueryObject(sObjectType);
}
// the two method names cannot match or you will get a compile fail
protected virtual Boolean getCanQueryObject(SObjectType sObjectType)
{
return sObjectType.getDescribe().isQueryable();
}
}
Then in your test, you can have a mock return always true or always false, as you wish.
@IsTest
class MyObjectHelperTests
{
class HelperMock extends MyObjectHelper
{
Boolean isQueryable = true;
protected override Boolean getCanQueryObject(SObjectType sObjectType)
{
return isQueryable;
}
}
@IsTest static void testCannotQuery()
{
HelperMock mock = new HelperMock();
mock.isQueryable = false;
MyObjectHelper.setMock(mock);
Test.startTest();
Boolean canQuery = MyObjectHelper.canQueryObject(...);
Test.stopTest();
system.assertEquals(false, canQuery, 'Some informative message');
}
}
add a comment |
I typically use a fairly simple pattern and don't bring in a framework. It would look something like the following:
public virtual with sharing class MyObjectHelper
{
static MyObjectHelper instance = new MyObjectHelper();
@TestVisible static void setMock(MyObjectHelper mock) { instance = mock; }
public static Boolean canQueryObject(SObjectType sObjectType)
{
return instance.getCanQueryObject(sObjectType);
}
// the two method names cannot match or you will get a compile fail
protected virtual Boolean getCanQueryObject(SObjectType sObjectType)
{
return sObjectType.getDescribe().isQueryable();
}
}
Then in your test, you can have a mock return always true or always false, as you wish.
@IsTest
class MyObjectHelperTests
{
class HelperMock extends MyObjectHelper
{
Boolean isQueryable = true;
protected override Boolean getCanQueryObject(SObjectType sObjectType)
{
return isQueryable;
}
}
@IsTest static void testCannotQuery()
{
HelperMock mock = new HelperMock();
mock.isQueryable = false;
MyObjectHelper.setMock(mock);
Test.startTest();
Boolean canQuery = MyObjectHelper.canQueryObject(...);
Test.stopTest();
system.assertEquals(false, canQuery, 'Some informative message');
}
}
I typically use a fairly simple pattern and don't bring in a framework. It would look something like the following:
public virtual with sharing class MyObjectHelper
{
static MyObjectHelper instance = new MyObjectHelper();
@TestVisible static void setMock(MyObjectHelper mock) { instance = mock; }
public static Boolean canQueryObject(SObjectType sObjectType)
{
return instance.getCanQueryObject(sObjectType);
}
// the two method names cannot match or you will get a compile fail
protected virtual Boolean getCanQueryObject(SObjectType sObjectType)
{
return sObjectType.getDescribe().isQueryable();
}
}
Then in your test, you can have a mock return always true or always false, as you wish.
@IsTest
class MyObjectHelperTests
{
class HelperMock extends MyObjectHelper
{
Boolean isQueryable = true;
protected override Boolean getCanQueryObject(SObjectType sObjectType)
{
return isQueryable;
}
}
@IsTest static void testCannotQuery()
{
HelperMock mock = new HelperMock();
mock.isQueryable = false;
MyObjectHelper.setMock(mock);
Test.startTest();
Boolean canQuery = MyObjectHelper.canQueryObject(...);
Test.stopTest();
system.assertEquals(false, canQuery, 'Some informative message');
}
}
answered 1 hour ago
Adrian Larson♦Adrian Larson
111k19121259
111k19121259
add a comment |
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f258841%2fis-there-a-way-to-fake-a-method-response-using-mock-or-stubs%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown