Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
340 views

IP Spoofing LG usage

Jump to solution

Hi,

We have 12.01 Environment, and planning to migrate to 12.53, want to know the IP Spoofing LGs usage, how it has been utiltized, how many tests are running per week with IP Spoofing enabled, and without IP Spoofing, and which team using more? So that we will plan the IP Spoofing migration based on the usage.

But how do we find the usage of IP Spoofing LGs, is there any way to do it. Please adivise. Thanks.

0 Likes
1 Solution

Accepted Solutions
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: IP Spoofing LG usage

Jump to solution

Hi

This was not an easy task to preform.

The problem is that this info resides in each project database, meaning that a singel sql can't be used, but it needs to be executed once in each project. This is no real problem, just tedious and scriptable.

Then there is the real problem. The information on wheter IPSpoofing is used or not, is stored on test-level and not saved on results-level. This means that if you ran a test first without ipspoofing, and then change the same test to use ipspoofing, there is no way to diffrentiate these two, you will count them as the test is configured at the time of the sql. I guess the information is available in the raw-results also but that information is not avlable from the database.

If these limitations are acceptable, here is a sql that will count how many runs is done with a test that has ipspoofing enabled (at this time not neccearily when executed).

use default_examle_db;

select count(*) Count , 'Yes' IPSpoofing from td.run run
inner join td.test on run.rn_test_id =test.ts_test_id and test.TS_PC_BLOB like '%<UseIPSpoofing>true%'
Union
select count(*) Count , 'No' IPSpoofing from td.run run
inner join td.test on run.rn_test_id =test.ts_test_id and test.TS_PC_BLOB like '%<UseIPSpoofing>false%'
;

Grouping on weeks, months or other fancy things is left to you

br /ola


Please mark post as solved if your problems or questions is/are resolved.
If this post was valuable to you, please consider kudo it.

.

View solution in original post

Tags (1)
1 Reply
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: IP Spoofing LG usage

Jump to solution

Hi

This was not an easy task to preform.

The problem is that this info resides in each project database, meaning that a singel sql can't be used, but it needs to be executed once in each project. This is no real problem, just tedious and scriptable.

Then there is the real problem. The information on wheter IPSpoofing is used or not, is stored on test-level and not saved on results-level. This means that if you ran a test first without ipspoofing, and then change the same test to use ipspoofing, there is no way to diffrentiate these two, you will count them as the test is configured at the time of the sql. I guess the information is available in the raw-results also but that information is not avlable from the database.

If these limitations are acceptable, here is a sql that will count how many runs is done with a test that has ipspoofing enabled (at this time not neccearily when executed).

use default_examle_db;

select count(*) Count , 'Yes' IPSpoofing from td.run run
inner join td.test on run.rn_test_id =test.ts_test_id and test.TS_PC_BLOB like '%<UseIPSpoofing>true%'
Union
select count(*) Count , 'No' IPSpoofing from td.run run
inner join td.test on run.rn_test_id =test.ts_test_id and test.TS_PC_BLOB like '%<UseIPSpoofing>false%'
;

Grouping on weeks, months or other fancy things is left to you

br /ola


Please mark post as solved if your problems or questions is/are resolved.
If this post was valuable to you, please consider kudo it.

.

View solution in original post

Tags (1)
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.