Testing Custom Software Integration - Sage Developer's License?

How do I test my custom software integration with Sage? Is there a Sage developers license? Do I have to buy a normal Sage license, even though I only need it for testing?

I'm specifically working with Sage 50 Canadian Edition, and part of my integration deals with payroll, so I would rather not have to pay the annual fee to maintain a regular payroll license, even though I only use it for testing my software.

  • As you say, testing will require access to a working copy of the software. There's an SDK agreement, but as far as I know it doesn't include access to Not For Resale software.

    There is an Accountants' Edition license that comes with software that can read and write all Editions of Sage 50, but it's not free.

    And there's a trial version that you can download.

    Sage software should be able to give you a better answer. This forum is primarily peer support, with moderators that work for Sage.
  • Thanks for your answer.

    Unfortunately, Sage has been unable to give me a better answer. I've called them and been redirected around several times, and nobody seems to know anything.

    I thought I would find other people in my situation here - are there any other developers out there dealing with this? How do they test their software, i.e. what's the general practice among others that build integrations?
  • I was a member of the DP Program from about 1996 or 1997 until they made it a free download.  At one point, they started distributing NFR copies for DPP members.  Since it went to a free download, there has been no open information available.

    I believe you would have to contact the manager of the DPP (used to be Paul Little but I don't know if that is still true now) or sign up for a paid version before you would get information, if any.  They had a generic email address for the DPP at one point but that was before the name change to Sage 50 so the email address probably changed as well.

    wfroese said:
    I thought I would find other people in my situation here - are there any other developers out there dealing with this? How do they test their software, i.e. what's the general practice among others that build integrations?

    Many of us are already business partners through the Certified Consultant program and therefore already have software to use through that program.  Others have clients who have asked for customer-specific programming and therefore they test on the client's computers.  There are a few larger companies also who may be part of the higher paid tiers of the DP program or hire consultants to help with the integration testing.

  • Well, as a developer, virtualization technology is quite much akin to a personal assistant using word processing. So as a developer, the need to test a CLEAN pc with just sage + my custom .net code is a must anyway. Once you install anything on a PC, then all bets are off as to a REAL test of your software and how you install it. So a VM is quite much a necessity.

    I developed quite an extensive interface from office (MS Access) using vb.net. So the Access application sends invoices into sage50.

    For testing I simply download a trial edition of sage50, and then install this 30 day trial into a Virtual machine (VM).

    After 30 days I simply re-install the trial edition into a fresh VM. For my testing, I really don’t care about much and even used the “test” customer that you are offered to “play” with when starting sage 50. So as a developer, I not really worried about keeping or maintains accounting data – but only require a test bed.

    So I downloaded the SDK’s for free, and had great success using the sag50 trial edition. In fact I quite much “like” having to re-install sage50 again, and this gives great opportunities to re-test my install of my .net code.

    The client of mine uses a licensed edition of sage50 in multi-user mode, but I never even bothered to ask for a copy since the download trial been sufficient for my development needs. They offered to get me a license for sage50, but I not needed it as of yet.

    So from sage, I can say that I been up and running with SDK development, and have done so for zero cost.

    For testing, I am thus using the free vitalization software (Oracle virtual box). I installed a copy of windows 7 into that VM. Because testing my installer code is required so very often, then it takes about 30 seconds to “clone” a fresh copy of windows 7.

    I then install sage 50 and then install my custom .net “invoice object” into that VM. I am using the free Inno installer and have quite a complex install + setup built. So lots and lots of testing of my “installs” is a good practice.

    So Virtual box, Inno installer, SDK's and even the sage 50 trial are all free. The only additional issue was having an extra copy of windows 7 for the VM.

    Albert D. Kallal
    Edmonton, Alberta Canada
    [email protected]