Comments (2)
Transcript from the discord chat, in case it helps someone else with the potential work around and for the background to this issue.
Anker01 — Today at 00:06
Also i have another question
In report the name of keyword documentation appear , and not the name of the Keyword
For example in my test case i used those keywords :
1) Given the user sends get on endpoint "/api/v1/"
2) Given the user sends POST on endpoint "/api/v1/" and body "{"label":"Temperature"}"
The report will show documentation keywords :
1) Send GET request to the given endpoint. Use this keyword when no headers nor query parameters needed.
2) Send POST request to the given endpoint. Use this keyword when no headers needed. Enable to write directly the body parameter in the keyword title.
is there any workaround to have the initial keyword in results , not documentation infos , because it is very confusing ? (edited)
damies13 — Today at 00:23
Yes there is sort of a work around, but only for custom keywords:
https://github.com/damies13/rfswarm/blob/master/Doc/Preparing_for_perf.md#keywords
I had actually thought about changing the behaviour at one stage to something similar to what you mentioned but it would have broken the ability to control the name the way it is now. Thinking about you example, I could probably add an option in the settings to alter the behaviour to report the keyword name.
Actually requests library was why I was thinking about it but when I investigated further I found requests library actually behaves differently to most other Robot framework libraries, so I kept the behaviour that works best for the majority of Robot framework libraries
If you want you can raise a feature request to add an option in the settings to alter the behaviour to report the keyword name. I guess if you do you can indicate if you think this would be better as a scenario wide setting or per script setting (I'm initially thinking it would be probably better as per script)
from rfswarm.
Note to self: Notes below for the changes need on the agent, this will need to be wrapped in an IF based on the setting in the manager gui, so this will need an RFS_ variable to pass the setting from the manager through the agent to the listener.
Anker01 — Today at 18:08
ok i was thiking to change : fd.append(" ResultName = attrs['doc']") to fd.append(" ResultName = name")
[18:08]
it will not temporarily do the job ? (edited)
damies13 — Today at 22:19
If you replace these 4 lines:
fd.append(" if self.msg is not None and 'message' in self.msg and not istrace:")
fd.append(" ResultName = self.msg['message']")
fd.append(" elif 'doc' in attrs and len(attrs['doc'])>0:")
fd.append(" ResultName = attrs['doc']")
With just
fd.append(" ResultName = name")
Yes that would do what you want and just report the keyword, after making that change make sure to delete RFSListener2.py as well to ensure it's recreated with the change
from rfswarm.
Related Issues (20)
- Data Table settings not loading correctly for new section HOT 2
- SQL generator creates invalid column for Name result in Metric type of Data Graph HOT 2
- Option to tell robot not to create the html & xml logs HOT 1
- Manager Fails to transfer resources to agent when test resource link in windows uses "Resource ../../../Resource/file.robot HOT 2
- Execption error thrown continuously in rfswarm-manager terminal HOT 8
- TPS is not grouping by second but rather milisecond HOT 2
- Issue with Variable Handling on Unix-style OS HOT 4
- Reporter hangs on launch HOT 2
- RFSwarm Agent doesn't fully release memory after uploading logs to Manager HOT 3
- Incorrect Test Case Matching with Double Quotes HOT 3
- Error in Test Execution: KeyError - 'Agents' in rfswarm_manager Module HOT 3
- Results change order in the table on the run tab HOT 1
- Document options for connecting agents to manager
- Make default test group settings configurable in scenario settings HOT 1
- Add SLA's
- Support for Environment Variable Substitution in Resources for rfswarm-manager HOT 3
- Icons not showing in the documentation
- rearrange documentation to make it easier to follow
- Add section for requests library `Get Resources` keyword
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rfswarm.