# Mender authentication integration with CI (a mock configuration)

**URL:** https://hub.mender.io/t/mender-authentication-integration-with-ci-a-mock-configuration/7119
**Category:** General Discussions
**Tags:** mender-client
**Created:** [August 20, 2024, 7:53am UTC](https://hub.mender.io/t/mender-authentication-integration-with-ci-a-mock-configuration/7119 "2024-08-20T07:53:31Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![adamstepniak41](https://avatars.discourse-cdn.com/v4/letter/a/b38774/32.png) [@adamstepniak41](https://hub.mender.io/u/adamstepniak41)
#### Post date: [August 20, 2024, 7:53am UTC](https://hub.mender.io/t/mender-authentication-integration-with-ci-a-mock-configuration/7119/1 "2024-08-20T07:53:31Z")

</div>

I would like to be able to perform some tests with MenderClient for the product that I’m currently working on, but without need to have full Mender configuration (A/B partition ect). Covering following test cases would help me:

1. Update MenderClient can connect to mender server (test mender client authentication)
2. MenderClient can fetch an artifact and verify signature against a key (test of mender client artifact verification)

Is there any way to stop other than update/verify steps by tweaking a configuration (creating effectively mock configuration)? Or there are already similar cases are covered by Mender tests?