polymer - web-component-tester progress has incorrect total -


the progress ring widget appears @ top right-hand corner of page when running web-component-tester seems show total number of tests 3x number of test suites, rather actual total of tests.

is known issue, or there can correct total show?

as example, in screenshot have 1 test in suite, yet when test finished, progress ring shows 33% completion:

enter image description here

i can see in code multireporter constructor estimated_tests_per_suite set 3 , multiplied number of test suites in order compute total used mocha html reporter render progress widget. appears onrunnerstart handler in multireporter supposed replace estimate current suite actual total, in testing runner argument passed handler multireporter object estimated total, updated total still estimate rather actual total.

unfortunately, haven't been able figure out why multireporter never computes correct total, nor have been able find hooks explicitly specifying total number of tests.


Comments

Post a Comment

Popular posts from this blog

toolbar - How to add link to user registration inside toobar in admin joomla 3 custom component -

im trying write component admin side , need add user creation. dont want duplicate existing codes add link. know how add task not simple link toolbar. thx help. if wanting button opens new user screen can try in component: $bar = jtoolbar::getinstance('toolbar'); $bar->appendbutton('link', 'users', 'new user','index.php?option=com_users&task=user.add'); you need add view.html.php file wherever you're creating toolbar. is need?
Read more

linux - disk space limitation when creating war file -

i have 1 gb disk space limitation hosting app , have used 700mb of it. however want create war file directory big (around 600mb) using command : jar -cvf root.war folderpath that's why encounter quota limitation , can't following. i'm looking way delete folder content when it's applying archive conserve disk space take note can't install zip tool in ssh shell ~ the code works on test directories, test first anyway, deletes files. it's not efficient. assumptions: 300mb free space, in destructively compress 600mb folderpath directory. none of files big -- if file in folderpath 300mb or larger, fail. notes: if ' $out ' file exists, nothing. first find pipes file list while , if ' $out ' doesn't exist in loop, create it, don't update -- if does exist, update it. each pass adds 1 more file, deletes unless file directory. after loop finishes delete empty directories too. unset u ; in=folderpath ; out=roo...
Read more