Test bed for new deprecations?

Hello, with the substantial API deprecations that were announced last week, will there be a test-bed on which we can test our proposed changes to ensure we have caught all possible deprecated access attempts before the main production service URL enacts the deprecation? If so, when (ish) and how might we access the test bed? Thanks.

To be clear, I understand that we can test the positive case (changed code) in the production instance. My question is whether we will have any mechanism to hand to test the completeness of our code so that any deprecated uses would be exposed before your deprecations go live in production.

Thanks!

Find more posts tagged with

Accepted answers

All comments

Isaac A.

Hi @sgolux!

In the Smartsheet API Reference, you can test each new endpoint directly in its query editor by clicking “Try it” below the example request.

I recommend checking the Change Log to find the replacement endpoints. Once you click into one, it will open in the API Reference where you’ll see the “Try it” option to run a live test.

I hope this helps!

Cheers,
Isaac.

sgolux

Thanks @Isaac A. -

I had been aware of this. Really what I mean is a test bed in which changes to accommodate the new deprecations can be tested prior to the actual deprecations going live.

Here is the potential scenario:

Between now and February, I go through our integration code (used by mutual customers of our platform and Smartsheet) and identify 10 places where we are using deprecated code and I make the changes in those 10 places to use the alternate/preferred solution.
However, because I am human, I fail to identify one additional place where I use some code that is deprecated.
I test my code against the current live version of the api, which allows both deprecated and preferred access. The test succeeds.
February 1 (or whatever the date is) rolls around, and the api is changed by truly deprecating all the endpoints as described.
My integration fails miserably because of the one place where I overlooked the need to make a change, and mutual customers of ours and of Smartsheet are left dead in the water while we scramble to make emergency patches to address the problem.

This would be I think a much better solution (differences in italics):

Between now and February, I go through our integration code (used by mutual customers of our platform and Smartsheet) and identify 10 places where we are using deprecated code and I make the changes in those 10 places to use the alternate/preferred solution.
However, because I am human, I fail to identify one additional place where I use some code that is deprecated.
I test my code against a test or staging version of the api, maybe at the URL api-new.smartsheet.com, instead of api.smartsheet.com, and immediately learn that I overlooked one deprecation in the code.
I fix that one place I missed at leisure.
February 1 (or whatever the date is) rolls around, and the api is changed by truly deprecating all the endpoints as described.
The integration continues to work, and our mutual customers are happy,

D. Stan Bright

Thanks @sgolux

Smartsheet API Team - we have exactly the same issue as described above and have been asking for a test environment for the past few years now, with no luck and many frustrated (common) customers.

Can you please seriously consider the above request?

Thanks.

Isaac A.

Hi @sgolux & @D. Stan Bright!

I’ve escalated this request to our Product team, and they let me know that they’ve heard your feedback and are taking it seriously. This is something the team is actively exploring and has on the roadmap, though it’s still in very early stages.

We don’t yet have a timeline to share, but you can expect updates as things progress.

Thank you for raising this and continuing to share your use cases, it really helps the team prioritize.

Cheers,
Isaac.

dmwang

I have the same issue. I would like an approach of replacing:

https://api.smartsheet.com/2.0/sheets with something like

https://api.new-smartsheet.com/2.0/sheets within all my workflows to see if they fail.

I cant detect all my workflows manually, and if i miss one, I'm gonna get fired.

Sign in to join the conversation!

Quick Links

Component react.discussion.discussions had an error.

ref must be one of: categoryID, siteSectionID, category, category/categoryID, category/name, category/description, category/url, category/allowedDiscussionTypes, locale, siteSection, siteSection/basePath, siteSection/contentLocale, siteSection/sectionGroup, siteSection/sectionID, siteSection/name, siteSection/description, siteSection/apps, siteSection/attributes, layoutViewType, discussionID, commentID, page, sort, discussion, discussion/name, tags, breadcrumbs, discussionApiParams, serverDraftID, serverDraft.