Skip to content

Conversation

@razumau
Copy link
Contributor

@razumau razumau commented Nov 3, 2025

Switches to a different test account in live specs (provisioned with Pandora), updates account setup instructions, cleans up a few unrelated things.

@razumau razumau force-pushed the jury.razumau/live_specs_3 branch from 1228c23 to f3044e5 Compare November 3, 2025 16:32
"Wed Feb 01 13:14:15 UTC 2012"
end
}
let(:parsed) { "2012-02-01 13:14:15 UTC" }
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is unrelated to the live specs change, I just noticed this very old and very unnecessary Ruby version check.

```

Then `bundle` as usual.
Then `bundle install` as usual.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bundle will stop working in Bundler 4.


[![Test](https://github.com/zendesk/zendesk_api_client_rb/workflows/Test/badge.svg)](https://github.com/zendesk/zendesk_api_client_rb/actions/workflows/main.yml?query=branch%3Amaster)
[![Gem Version](https://badge.fury.io/rb/zendesk_api.svg)](https://badge.fury.io/rb/zendesk_api)
[![Code Climate](https://codeclimate.com/github/zendesk/zendesk_api_client_rb.svg)](https://codeclimate.com/github/zendesk/zendesk_api_client_rb)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn‘t work anymore and I don’t think we need to revive it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏼 they don’t do open source scans anymore.

SPEC_LIVE_ZENDESK_HOST: ${{ secrets.SPEC_LIVE_ZENDESK_HOST }}
SPEC_LIVE_USERNAME: ${{ secrets.SPEC_LIVE_USERNAME_NEW }}
SPEC_LIVE_PASSWORD: ${{ secrets.SPEC_LIVE_PASSWORD_NEW }}
SPEC_LIVE_ZENDESK_HOST: ${{ secrets.SPEC_LIVE_ZENDESK_HOST_NEW }}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’ll replace current SPEC_LIVE_USERNAME etc. values and use them again after this PR is approved (and before merging it).

it_should_be_readable current_user, :assigned_tickets, create: true
it_should_be_readable agent, :ccd_tickets, create: true
it_should_be_readable current_user, :assigned_tickets
it_should_be_readable agent, :ccd_tickets
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven’t full figured out why creation fails now, but we never created these users from here anyway (we create these users and assign and CC tickets during manual setup).

@razumau razumau force-pushed the jury.razumau/live_specs_3 branch from f3044e5 to 067671d Compare November 4, 2025 11:01
@razumau razumau marked this pull request as ready for review November 4, 2025 11:05
@razumau razumau requested a review from a team as a code owner November 4, 2025 11:05
@razumau razumau requested a review from a team November 4, 2025 11:05
def valid_attributes
{
:category_id => "3",
:category_id => "9903501961242",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this the category id from the new test account?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. I don’t know why it worked with an account-specific like "3" before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants