How to fix the ExampleInstrumentedTest error at “debug” to “release” switch?

Even the simpliest application displaying "Hello world" (I've just created a project in Android Studio 3.2.1 and didn't add a line of code), when I switch Build Variants from "debug" to "release" the ExampleInstrumentedTest I getting the error in the ExampleInstrumentedTest already at import stage:

import org.junit.Test;

import org.junit.runner.RunWith;

import static org.junit.Assert.*;

screenshot: https://yadi.sk/d/tqpOqahoER9r7Q

If I return to "debug" - everything becomes perfect again: https://yadi.sk/d/1nKRraRqEnv2Bg

In the build.gradle (Module:App) dependencies:

testImplementation 'junit:junit:4.12'

androidTestImplementation 'com.android.support.test:runner:1.0.2'

androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'

exists https://yadi.sk/d/U_1HzgA1AONgoA

How is possible to fix it?

edited Jan 1 at 18:07

Fantômas

32.8k156390

asked Jan 1 at 15:24

Slava

add a comment |

import org.junit.Test;

import org.junit.runner.RunWith;

import static org.junit.Assert.*;

screenshot: https://yadi.sk/d/tqpOqahoER9r7Q

If I return to "debug" - everything becomes perfect again: https://yadi.sk/d/1nKRraRqEnv2Bg

In the build.gradle (Module:App) dependencies:

testImplementation 'junit:junit:4.12'

androidTestImplementation 'com.android.support.test:runner:1.0.2'

androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'

exists https://yadi.sk/d/U_1HzgA1AONgoA

How is possible to fix it?

edited Jan 1 at 18:07

Fantômas

32.8k156390

asked Jan 1 at 15:24

Slava

add a comment |

import org.junit.Test;

import org.junit.runner.RunWith;

import static org.junit.Assert.*;

screenshot: https://yadi.sk/d/tqpOqahoER9r7Q

If I return to "debug" - everything becomes perfect again: https://yadi.sk/d/1nKRraRqEnv2Bg

In the build.gradle (Module:App) dependencies:

testImplementation 'junit:junit:4.12'

androidTestImplementation 'com.android.support.test:runner:1.0.2'

androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'

exists https://yadi.sk/d/U_1HzgA1AONgoA

How is possible to fix it?

edited Jan 1 at 18:07

Fantômas

32.8k156390

asked Jan 1 at 15:24

Slava

import org.junit.Test;

import org.junit.runner.RunWith;

import static org.junit.Assert.*;

screenshot: https://yadi.sk/d/tqpOqahoER9r7Q

If I return to "debug" - everything becomes perfect again: https://yadi.sk/d/1nKRraRqEnv2Bg

In the build.gradle (Module:App) dependencies:

testImplementation 'junit:junit:4.12'

androidTestImplementation 'com.android.support.test:runner:1.0.2'

androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'

exists https://yadi.sk/d/U_1HzgA1AONgoA

How is possible to fix it?

android

edited Jan 1 at 18:07

Fantômas

32.8k156390

asked Jan 1 at 15:24

Slava

edited Jan 1 at 18:07

Fantômas

32.8k156390

asked Jan 1 at 15:24

Slava

edited Jan 1 at 18:07

Fantômas

32.8k156390

edited Jan 1 at 18:07

Fantômas

32.8k156390

edited Jan 1 at 18:07

Fantômas

32.8k156390

asked Jan 1 at 15:24

Slava

asked Jan 1 at 15:24

Slava

asked Jan 1 at 15:24

Slava

add a comment |

1 Answer
1

active

oldest

votes

unit tests are not meant to run in release mode.

in best cause you could change the test build-type; for example:

testBuildType "staging"

I'd doubt this would work with release, since that build-type has to inherit from build-type debug.

answered Jan 1 at 15:38

Martin Zeitler

18.7k34372

add a comment |

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53996629%2fhow-to-fix-the-exampleinstrumentedtest-error-at-debug-to-release-switch%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

unit tests are not meant to run in release mode.

in best cause you could change the test build-type; for example:

testBuildType "staging"

I'd doubt this would work with release, since that build-type has to inherit from build-type debug.

answered Jan 1 at 15:38

Martin Zeitler

18.7k34372

add a comment |

unit tests are not meant to run in release mode.

in best cause you could change the test build-type; for example:

testBuildType "staging"

I'd doubt this would work with release, since that build-type has to inherit from build-type debug.

answered Jan 1 at 15:38

Martin Zeitler

18.7k34372

add a comment |

unit tests are not meant to run in release mode.

in best cause you could change the test build-type; for example:

testBuildType "staging"

I'd doubt this would work with release, since that build-type has to inherit from build-type debug.

answered Jan 1 at 15:38

Martin Zeitler

18.7k34372

unit tests are not meant to run in release mode.

in best cause you could change the test build-type; for example:

testBuildType "staging"

I'd doubt this would work with release, since that build-type has to inherit from build-type debug.

answered Jan 1 at 15:38

Martin Zeitler

18.7k34372

answered Jan 1 at 15:38

Martin Zeitler

18.7k34372

answered Jan 1 at 15:38

Martin Zeitler

18.7k34372

answered Jan 1 at 15:38

Martin Zeitler

18.7k34372

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

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.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

Search This Blog

Ufyukyu