Cloud Platform

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Not under consideration
Categories Performance Tester
Created by Guest
Created on Aug 5, 2021

pre-populate Test->Recording->Proxy Recording filters with well known junk domains

RPT allows the use of filters when recording to filter out domains at recording time so they don't have to be filtered out at test generation time.


The problem is this list is empty, and a bit tricky to use


Refer to junk1.jpg for the Preference in question

--

What are the well known junk domains? Depends on the browser:


  • junk2.jpg shows junk domains captured by recording with Firefox. I didn't go to any websites when recording, just let FF sit there and let the packets get recorded

  • junk3_EE.jpg shows the junk domains captured by recording with EE. Same MO: record but don't do anything and let the packet count rise

  • junk4_chrome.jpg is the same when recording with Chrome

Why is it useful?

This is very useful:

  1. time would be saved at test generation time because these well known junk domains won't be captured at all then thus don't need to be filtered out

  2. the recording will be smaller. With EE, Chrome, and MS Edge, RPT sets the recording proxy by setting the Windows system proxy, so a lot of traffic gets captured that's useless. Smaller tests mean quicker test generation time

  3. no need to edit browser settings to try to avoid some of these domains. Example: turning off Firefox Data Collection and Use will avoid some, but not all, junk traffic being captured

4. Sure the list of filtered domains can be remembered at test generation time, but this list of filtered domains never makes it to the Windows->Preferences->est->Recording->Proxy Recording list of filters.

5. if someone forgets to filter out junk domains in their test they would need to regenerate the test again, this time to filter out junk domains.


We know that junk domains will be captured, let's filter them out up front. Junk domains are annoying, and some tests have a lot of domains in them, distinguishing them from junk ones is time consuming and prone to error






Who would benefit from this IDEA? anyone who does a recording with RPT
Idea Priority Medium