New to Kiwi TCMS and running through tutorial.
In https://kiwitcms.readthedocs.io/en/latest/guide/testplan.html#default-components, it explains a 'Default Components' tab in test plan. Problem is, the tab is missing in our Kiwi setup. Cannot find related steps in documentation about this either.
Is there a setting/process not discussed in documentation to enable it?
It was removed in:
https://github.com/kiwitcms/Kiwi/commit/09321236ee2ecbdfc2d001a0e1e28b0504c30171
Remove TestPlan components functionality
this functionality was never used and never intended to be used in
such a way. Components are something that is attached to test cases
not test plans!
Related
I'm working my way through the wonderful Serverless Stack Tutorial, and I reached the chapter on using a React ErrorBoundary to view debug information. In the chapter, it describes how one should see debug information when running the application locally (as shown below in this image from the chapter).
I've made sure that I've copied the code and set it up correctly. However, I'm not seeing the debug information in my local debug instance. I only see the fallback UI:
I'm wondering if I'm using a later version of either React or other services than used in the tutorial. I've committed my code to a separate branch in case anyone would be willing to pull/fork and try it. I'd appreciate any assistance.
Update
I found my way to this Github issue describing changes in behavior between React 17 and React 18. The issue led to this CodeSandbox example. I noticed one of the examples displayed an overlay which looked similar to the one in the tutorial example. I saw this text at the bottom:
This screen is visible only in development. It will not appear if the app crashes in production.
Open your browser’s developer console to further inspect this error.
This error overlay is powered by `react-error-overlay` used in `create-react-app`.
Searching for react-error-overlay led me to this package. I can see this package is included in my code as installed per the tutorials instructions. However, it does not seem to be running to display errors during development.
I don’t know what happen to my WebStorm settings but previously whenever I add new react component it gave me a warning by adding underline above the component name. But now it is not showing any warnings. Why?
Please see my screenshot example currently in screenshot function is not defined so it gives underline.
How to reset the setting?
In screenshot I added Button,Dialog,DialogTitle but not imported. It is not giving any warning, why?
We intentionally decided not to mark the components as unresolved because there were quite a lot of patterns of defining the React components, especially in the component libraries that WebStorm couldn't recognize. So instead we decided to only show the missing import inspection for the cases where we knew where the component was defined.
We will review of how it all works now and will enable the inspection if it doesn't generate too much false positives.
Please vote for WEB-32549 to be notified on any progress with this feature
Recently I've been setting up a development stack for React using Webpack (new for me) and of course wanted to benefit from all of the shiny conveniences that it provides (which are by the way great!). Among tons of resources I dug on the internet, the particularly good one I found was the React Webpack Cookbook, with which every step went like clockwork. However I stumbled across a hitch that has been taking me several hours to try to solve, not being able to find a solution in the aforementioned page, nor any other source: the expose-loader wouldn't expose React to global scope in Chrome (not tested on other browsers) therefore not allowing React DevTools extension to run. I tried mixing all the steps from the Cookbook, using different versions of React, minified/unprocessed, nothing worked.
The problem was trivial when discovered, but the source of the problem tricky to find: all the time I was using the localhost:8080/webpack-dev-server/ version of my development page, as suggested by the Cookbook, because it allowed me not to bother with the inability to inject <script src="http://localhost:8080/webpack-dev-server.js"></script> into html-webpack-plugin index file generator and provided sort of a nice status bar. It works perfectly since I switched to localhost:8080. Unfortunatelly I wasn't able to make it work with the localhost:8080/webpack-dev-server/ version, though I think it has something to do with the fact that under this url the page is loaded into a frame.
I have followed the MUI guide provided here: http://mui.codeplex.com/wikipage?title=How%20to%20use%20your%20own%20navigation%20framework
but that doesn't work because the BlankWindow resource is not available.
Then someone aswked about it here: http://mui.codeplex.com/workitem/19663
and the developer replied that the user should recompile the library using the latest source code.
I've downloaded the latest source code from here: http://mui.codeplex.com/SourceControl/latest
but upon compilation, the resulting library is the same that's distributed online.
So at the moment I am confused in regard to solving this issue. Could anyone provide some support please?
Do you use Resharper?
Look here, this is maybe only designer problem.
I have the same issue... But I can normaly build and run my application.
They say:
Weird. I am having the same issue on my machine (VS2012 + Resharper).
It works fine when I run it but it's failing to build in TeamCity. Ill
keep investigating...
I am running a program created via the MUI template in VS. Try to
remove it from resharper error/warning. Resharper can force a simple
warning to an error if a wrong setting is set.
Protractor seems to be getting better every week and I am now using the 0.24 version. Unfortunately I was not able to find out how I can simulate clicking a value from a <select> list.
Can someone give me an example of how they select a value from a populated <select> or even better point me to a place in the documentation where this is explained. For reference I did see the question: How to select option in drop down protractorjs e2e tests however as things are changing so quickly I would like to know is if using xpath is still the recommended way to do a select or have any users come up with a better solutions with the latest version of Protractor. As I have a lot of coding to do I would like to be sure I am using the best approach.
I have adapted the code from #PaulL in How to select option in drop down protractorjs e2e tests.
var selectDropdownbyNum = function (selectElement, optionNum) {
if (optionNum){
selectElement.all(by.tagName('option'))
.then(function(options){
options[optionNum].click();
});
}
};
Protractor 0.24.0 "is a big change with lots of breaking stuff". There are described by Julie Ralph (the protractor main developer) in this g+ post.
I follow her on google+ to be notified of the new releases.
In this case findElements have been replaced by all.
Finding good documentations is quite difficult. Often, i walk through the protractor specs on github to find working examples.
I used by.css and it worked fine for me.
actionPage.findElement(protractor.By.css('.NEW_CLAUSE_PANEL div:nth-child(2) span select option:nth-child(3)')).click()