Testing configuration after copying a BBP client

After copying an BBP client (i.e. Production to Test), what would be the logical steps to take to ensure the Test...

client's config is correct?

There are a number of tables and transactions that need modifications in the EBP system post a refresh from a production system. Some of it depends on what all functionalities you're using in your EBP implementation. Here are some areas: Logical System, RFC Destinations, TCP/IP Destinations, OrgStructure Attributes (The most amount of changes are here), Replicated Vendor & Master data source destination changes, the IMG destinations changes. So as you can see the answer is not very simple. You need to work with your EBP technical & BASIS team to develop a post-refresh procedure. And the key here is also that certain tasks in this procedure need to be executed in a chronological manner, otherwise things wont work as desired. Typically once I've developed the procedure with a client understanding their functionality, I would typically allocate 1/2 day to a day for successfully executing this procedure and testing your results. Again the majority of the work lies in developing the procedure.