Test progress shows 0 percent complete - kiwi-tcms

All of my test runs are showing as in the attached image - in this case all tests have passed, but I am showing 0% progress for the test run.
When I initially start the test run, the progress bar updates - but subsequently disappears.
I don't have any other issues with test data, test cases, plans, etc.

For the record this is tracked here and we're working on this area
https://github.com/kiwitcms/Kiwi/issues/1326

Related

How to set test coverage threshold of new code only (Jest)

How to set coverage checking of every new chunk of code before merging and skip this particular merge if test coverage of new code in it is less than 80%? We already have the global threshold of 80% but this setting doesn't assume that each pull request will be covered with tests less than 80% (some can be covered with 60% and some with 100% - it's unfair).
Stack (React, Next, Jest)
Thanks for the help!

huggingface_load_dataset() function quit() without finishing

I try to use datasets to get "wikipedia/20200501.en" with the code below.The progress bar shows that I just complete 11% of the total dataset, however the script quit without any output in standard outut. I checked the cached directory and find the arrow file is just not completed.
wiki = load_dataset("wikipedia", "20200501.en", split="train", download_config=download_conf)
I tried several times and got different ratio of completion but never succeed in completing the progress.Could any one help me?
env:python version:3.7
datasets version:1.1.2
MacOS
This is caused by unstable network connection. It can be solved by downloading the URL with browser or "wget" function.

After changing test case, test case in test run not changed. Does it work as designed?

Add a test case to a test run, then change test cases, e.g., steps, or expected results. But test case in test run displays changed before.
At first, I think it maybe a bug. Discuss with my workmate, he think it right. Test run keep a copy after test case add to run.
Yes, seems reasonable. Does this as designed?
This is working as designed. TestRun keeps a copy of the TestCase text from the time when TR was created. You see for build 1 I may want a very basic test for say the login screen, but for build 2, 3, etc I want to improve this.
This is why such functionality exists.
In TestRun page there is the Cases -> Update menu which will refresh TestCase text for IDLE entries.
For the ones that have already been executed either change them to IDLE before update or just create a new TestRun.

How to wait for DOM to load in protractor tests

I am hitting the url in browser by "browser.get(url)" and then I am expecting something to be present on the screen. But My test cases are failing because it is taking some time to load the page and test cases are executed before the page loads. So is there a way where I can wait for DOM to load and then the rest of the test cases are executed. I do not want to put sleep as the time to load the page is not consistent and it is unnecessary delay in executing the tests.
I am looking for some solution where we can wait for DOM to load and then we go to next tests to execute.
I solved this by waiting for some specific element to be present on the screen and then perform next activity: here is the code, how I am waiting for the element:
browser.wait(function(){
return browser.driver.isElementPresent(by.id(elementId));
},30000);
So, if you have doubt that execution can happen before the element is present on the screen, then just wait for some element to be present on the screen and then perform next activity.
Hope this will help other, who will face same kind of issues.
You can put a timeout for the script in your config
jasmineNodeOpts: {defaultTimeoutInterval: 70000}
This will wait AT MAX for specified time.

Response time loading is not correct

i can record the simulation through Gatling and able to run the simulation, but i am getting less load time compared to actual UI (User Interface) when generating the reports.
In my case actual load time when i click on some button(one request,it internally loads some data) on UI is almost 3 to 4 mins, but in reports it will show 300 ms...
i can clicked the button then it will take 2 to 4 minutes after that it open one excel, this during time not coming the reports, the reports giving time 300 or 360 ms.
the button url placed script in scala and run again but it gives wrong loading time(360 ms)
Thanks in advance,
any suggestions are helpful to me.

Resources