bwennekes
New Contributor
Joined 8 years ago
User Profile
User Widgets
Contributions
Re: Saving without property values
@GillerM Finally I have ReadyAPI 2.3.0 available at my workplace. Unfortunately the new functionality is different from how I hoped it would work (the documentation seems correct though). Setting 'Save Properties Between Sessions' to false resets the values after each run, which makes debugging and finding out where something went wrong after the run a real pain. So this creates a new problem. If there's something I missed here please say so. For now this seems to 'break' more than it fixes and thus it is not a solution to the problem. The problem being: (properties with) run data should not be saved as this creates merge conflicts. But run data should be available for debugging.7.8KViews0likes0CommentsRe: In ReadyAPI 2.3.0 I can't see any log output
I was having similar problems and did some research to find out what could be the cause. I found out with the code below (put it in a groovy step and run) that info was not enabled. Errors I did still see though. def isInfoOn = log.isInfoEnabled() log.error(isInfoOn) So next I enabled the info logging and tried again: import org.apache.log4j.Logger import org.apache.log4j.Level log.setLevel(Level.INFO) log.info("hi") That did work for me, but then I had to enable it every time, which was not much of a solution. After some more digging I found the 'soapui-log4j.xml' in my bin folder inside the ReadyAPI folder. This is apparently where the level of logging is set for all different types. I set the logging level of root to INFO (at the bottom in my case) and that did the trick!3KViews1like1CommentRe: Saving without property values
GillerM I noticed this new feature in the 'What's New in ReadyAPI 2.3' already. It does seem that this will solve the above mentioned problem, though a bit less flexible than the suggested solution. Hopefully my IT department will roll out this version soon so I can start working with it!8.1KViews0likes0CommentsSaving without property values
To extend the composite project functionality and improve the way ReadyAPI’s XML-files can be version controlled I would like an option to save without property values. Ideally this option can be enabled/disabled for properties defined at Test Step, -Case, -Suite and -Project level with a checkbox. Currently there is only the option to ‘discard values on save’, which is only available on Test Step level. Discarding values on save can be quite cumbersome if you need the values making changes/corrections while still wanting to save often. This could mean that you need to rerun the whole project after a change is saved, which in my case may take more than half an hour. At this time I’m still using the ‘discard values on save’ option by lack of alternatives. This also means that all properties in the project must be defined at step level, the only place where this option is available. This in turn means we cannot use functionality like the ‘Run Test Case’ Test Step as this uses properties on Test Case level, which is a real shame. In my opinion just running and saving the ReadyAPI project should not change the project XML. As this currently does happen it creates hundreds of changes and merge conflicts without any functional changes in the ReadyAPI project.9.7KViews23likes13CommentsVersion control and properties
Hello, Currently I'm part of a team of testers working together on a single ReadyAPI composite project which is version controlled by SVN. To make merging as painless as possible we enabled options like ‘Pretty print project files’ and ‘Trim WSDL’. One thing that is still a problem for us though, is the properties. In our case all properties (except on project level) are filled with run data, which changes every run. And every time we save the project all these changed properties are causing numerous of conflicts. This in turn makes merging a painfully slow process. In our team we have discussed a (non-existing) option like “do not save properties” which can ideally be set at test step, -case, -suite and -project level. Which in our eyes is quite different from the “discard values on save” option. Discarding on save might be an alternative if the option was available on all levels. That is apart from the fact that we find it really annoying because you lose all run data every time you save. This might lead to rerunning the whole test project (which takes half an hour) every time you save, or collecting multiple changes before saving with the risk of losing them. As our way of working does not seem very special we would like to hear if others are experiencing the same problems with properties and version control and how they are circumventing or tackling this. Regards1.3KViews0likes1Comment