cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

User testing/signoff procedures

Jelena_Perfiljeva
Active Contributor
0 Likes
3,479

Most likely every SAP client has some kind of a procedure in place for the user testing and signoff before the transports may be moved to production. From your experience, what procedures have you seen (not just in the SAP world) and which ones, in your opinion, work the best?

Here are two examples from my past jobs as a programmer:

1) Developer prepares testing scenarios (in Excel); Business Analyst runs them through and marks each line with the result. This spreadsheet is then embedded in another document that lists all the items to be implemented in that week (scheduled weekly implementation).

2) A signoff form (Word template) is prepared by developer/functional analyst and emailed to the business user responsible for testing. The form includes basic information (usualy there is a corresponding ticket) and developer's name/date as form of a signature. The user then signs/dates the form and returns it to the developer. The form is forwarded to Basis admin as an approval to move the transports.

In perfect world, the signoff should not be an additional burden for a developer yet need to ensure that testing has been performed properly. In reality, this may be difficult to achieve. As a developer, I liked the 2nd option better, but it sometimes lead to users signing off without any testing (and then guess who gets blamed when something doesn't work).

What are your thoughts?

View Entire Topic
Jelena_Perfiljeva
Active Contributor
0 Likes

Thanks for a reply, Rob.

When the users signoff on something, how complex that step usually is? Is it just an email like "yes, I approve it" or is there a Word/Excel document (like in my examples) used? Or is it something more complex, e.g. a workflow or a special software?

Also I'm curious what evidence (if any) is usually expected from the users as evidence of testing?

Former Member
0 Likes

We rely on an e-mail from the users. While this may or may not indicate just how much testing was done, the important thing is that it satisfies the auditors. When they ask to look at a transport, we are able to show them the original request, the transport log and the sign-off.

QED

Rob