|
Users. We have a group of "super users". One of thier functions is to provide testing of code changes, whether in house developed or application vendor developed. Of course, IT ensures that the "one" bug fixed actually solved that problem before releasing to the super users. We usually have "enhancement" testing about every other month for some reason or other. It takes about 4 hours each time. Kevin Fox kdfox@xxxxxxxxxxxxx -----Original Message----- From: mapics-l-bounces@xxxxxxxxxxxx [mailto:mapics-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Neely Sent: Friday, June 10, 2005 1:11 PM To: MAPICS ERP System Discussion Subject: RE: Applying client fix to PowerLink/Browser Kevin, Is the I.T. group doing the testing? Or, are the users doing the testing? Thanks "Kevin Fox" <kdfox@xxxxxxxxxxxxx> Sent by: mapics-l-bounces@xxxxxxxxxxxx 06/10/2005 03:02 PM Please respond to MAPICS ERP System Discussion <mapics-l@xxxxxxxxxxxx> To "'MAPICS ERP System Discussion'" <mapics-l@xxxxxxxxxxxx> cc Subject RE: Applying client fix to PowerLink/Browser Chris, We apply on our training class room machines and us against the test and training environment. We have a standard training script that covers most issues that are unique to us. If we don't find any issues, we release to production. Kevin Fox kdfox@xxxxxxxxxxxxx -----Original Message----- From: mapics-l-bounces@xxxxxxxxxxxx [mailto:mapics-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Neely Sent: Friday, June 10, 2005 12:28 PM To: mapics-l@xxxxxxxxxxxx Subject: Applying client fix to PowerLink/Browser When you download and apply the latest client ptf to fix one problem, are you performing system wide(across all client applications) Browser testing to make sure the new client ptf does not screw up something else? Or, are you just checking to see if it fixed the problem you were originally looking to fix? Unlike on the server side, you can't just apply the ptf that fixes your particular problem. What are most people doing in this case? Thanks _______________________________________________ This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a message email: MAPICS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/mapics-l or email: MAPICS-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/mapics-l. _______________________________________________ This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a message email: MAPICS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/mapics-l or email: MAPICS-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/mapics-l. _______________________________________________ This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a message email: MAPICS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/mapics-l or email: MAPICS-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/mapics-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.