Reuse transaction to other script

after recording login transaction, it will be used in many scripts. So I thought we could store the login transaction to external JS as a function and other scripts could load it.

but the cons are that if we need to update the transaction, we cannot open it to Vugen to check the header/response/etc.

We could add the file to the script via Extra Files but that means it will be added to the script folder not in the original path and for any changes we make, we have to update it manually to the file in the original path.

Could there be another way to maximize the transaction reusability?

Parents
  • Suggested Answer

    0  

    , it is not that easy to share common scripts like the one for general login into business applications.We have the same issue. We solved in the following way:

    1. Maintain for common protocols (C, JS, DevWeb, TC) template scripts that contain common topics like Login, Sending each transaction to Influx, etc.
    2. Templates are stored in source code repository
    3. Various teams are encourage maintain their scripts in source code repository as well and can merge easily the templates into their code bases.

    How to ask questions

    Reward contributions via likes or 'verified answers'

Reply
  • Suggested Answer

    0  

    , it is not that easy to share common scripts like the one for general login into business applications.We have the same issue. We solved in the following way:

    1. Maintain for common protocols (C, JS, DevWeb, TC) template scripts that contain common topics like Login, Sending each transaction to Influx, etc.
    2. Templates are stored in source code repository
    3. Various teams are encourage maintain their scripts in source code repository as well and can merge easily the templates into their code bases.

    How to ask questions

    Reward contributions via likes or 'verified answers'

Children
No Data