Subject7 and Jenkins - parameterized URL, user id, and password
We have separate URLs and login information for the development, test, and training environments. These environments are identical other than the URL and login information.
We would like to parameterize these URLs so that they could be triggered from Jenkins by the deployment manager. We would like to remove the hard-coded URL and login information from the test cases. The idea is to use the same test case for multiple environments without creating redundancy in either Subject7 or Jenkins.
We would like the presence of keywords in URL ("test", "dev" etc.) to invoke a separate login module and corresponding username password combo.
Please sign in to leave a comment.