On Saturday, 14 February 2015 at 10:25:52 UTC, Vladimir Panteleev
wrote:
make it stop using its own templating language and use the one
we already use for everything else - HTML, PDF, Mobi, CHM -
DDoc.
DDoc isn't a good tool to generate webpages. For the simple
reason that a webpage needs to be
On 2/14/15 5:19 AM, Sönke Ludwig wrote:
Am 14.02.2015 um 09:46 schrieb Andrei Alexandrescu:
Per the screenshot at http://i.imgur.com/6lY57L6.png, the entire
/library/ and /library-prerelease/ part of the website is not rendering
properly at least in Chrome and Firefox on OSX.
Folks, there needs
On 2015-02-14 10:04, Rikki Cattermole wrote:
It might be wise to start setting up some form or web site testing.
Like PhantomJS[0].
PhantomJS will only cover the WebKit engine. I guess it's better than
nothing. For other browser engines there's a service called Saucelabs
[1] that supports a
On 2015-02-14 10:48, Vladimir Panteleev wrote:
Can you write a PhantomJS test that checks whether a web page "looks
broken"?
No, the only thing one can do is take screenshots and look at them
manually or compare them with a previous state if similar.
--
/Jacob Carlborg
Am 14.02.2015 um 09:46 schrieb Andrei Alexandrescu:
Per the screenshot at http://i.imgur.com/6lY57L6.png, the entire
/library/ and /library-prerelease/ part of the website is not rendering
properly at least in Chrome and Firefox on OSX.
Folks, there needs to be some visual testing with each pull
On Saturday, 14 February 2015 at 11:08:18 UTC, Vladimir Panteleev
wrote:
On Saturday, 14 February 2015 at 10:46:07 UTC, John Colvin
wrote:
On Saturday, 14 February 2015 at 08:46:58 UTC, Andrei
Alexandrescu wrote:
Per the screenshot at http://i.imgur.com/6lY57L6.png, the
entire /library/ and /li
On Saturday, 14 February 2015 at 10:46:07 UTC, John Colvin wrote:
On Saturday, 14 February 2015 at 08:46:58 UTC, Andrei
Alexandrescu wrote:
Per the screenshot at http://i.imgur.com/6lY57L6.png, the
entire /library/ and /library-prerelease/ part of the website
is not rendering properly at least
On Saturday, 14 February 2015 at 08:46:58 UTC, Andrei
Alexandrescu wrote:
Per the screenshot at http://i.imgur.com/6lY57L6.png, the
entire /library/ and /library-prerelease/ part of the website
is not rendering properly at least in Chrome and Firefox on OSX.
All looks fine to me on up-to-date
On Saturday, 14 February 2015 at 09:04:55 UTC, Rikki Cattermole
wrote:
I don't know how doable, but set it up to so it would auto
submit the images to the github PR would be awesome.
That would be nice. Currently people have to do this by hand.
This doesn't even need to have screenshots or use
On Saturday, 14 February 2015 at 10:08:16 UTC, Rikki Cattermole
wrote:
Anyone with DOM + javascript experience could. But it would be
more of a set of unit tests then anything else.
No, you have missed my point. without an AI, it is impossible to
write a general test to check that the webpage
On 14/02/2015 10:48 p.m., Vladimir Panteleev wrote:
On Saturday, 14 February 2015 at 09:04:55 UTC, Rikki Cattermole wrote:
It might be wise to start setting up some form or web site testing.
Like PhantomJS[0].
Can you write a PhantomJS test that checks whether a web page "looks
broken"?
Any
On Saturday, 14 February 2015 at 09:04:55 UTC, Rikki Cattermole
wrote:
It might be wise to start setting up some form or web site
testing.
Like PhantomJS[0].
Can you write a PhantomJS test that checks whether a web page
"looks broken"?
On 14/02/2015 9:46 p.m., Andrei Alexandrescu wrote:
Per the screenshot at http://i.imgur.com/6lY57L6.png, the entire
/library/ and /library-prerelease/ part of the website is not rendering
properly at least in Chrome and Firefox on OSX.
Folks, there needs to be some visual testing with each pull
Per the screenshot at http://i.imgur.com/6lY57L6.png, the entire
/library/ and /library-prerelease/ part of the website is not rendering
properly at least in Chrome and Firefox on OSX.
Folks, there needs to be some visual testing with each pull request.
This is one of the places where automate
14 matches
Mail list logo
