Name: CSS 用のテストを書くことは可能!噂を信じてはいけない - Gil Tayar｜CSSconf EU 2019 (Writing Tests For CSS Is Possible! Don’t Believe The Rumors - Gil Tayar | CSSconf EU 2019)
Uploaded: 2021-01-14T10:26:05.000Z
Duration: 27 min 1 s
Description: VoiceTubeの動画で発音を聞きながら英語表現を覚えよう！学べる英語：

I have to say I'm not Ah, I'm not a front and developer.

I've been switching back and forth between front and back end.

Currently, I'm in my back and face and the presentation is not loading.

Hopefully, uh, but one thing I didn't notice both in Jing's presentation and in Jason's is this Did everybody knows that they were both showing us how responsive the things are.

Says that that's problematic because I have to check it every time, time and time again.

Are, uh, testing is is what is has been my passion since about 2000.

I'm a developer, advocate and a software developer, mostly software developer at Apple Tools.

And what we do is we specialize in visual testing tools.

And we'll talk about fear of what in a sec.

But first, I want to talk about web developers first.

Let's start with the back and developers back.

And developers have been there since before the Web and I'ma back in developer.

Right now, they use words like, you know, thread pools and message cues and scholars and you know they're back there.

And without them, come on way wouldn't be able to do our friend so round of applause.

What about front and front and is divided front.

And let's talk about front and JavaScript with developers.

They deal with things like a JavaScript and angular and react and States management and Darman and all that kind of stuff.

And the way they handled things about front and CSS developers, front entrances.

That's where you come on a round of applause for you.

Not only are you all beautiful, you create beautiful things using CSS, and I'm constantly amazed by these things and how you managed to work with them s So you deal with responsive design, media queries and flex box, and something has wonderful is happening in the Web development world.

Developers are starting to write tests the test their own code.

This has been true for something like five years or so.

Obviously enough people been testing before that, but it's become slightly mainstream of the last five or seven years.

Anybody know what a go program a phobia is probably not given that I've just invented it.

Okay, it's, uh and I will explain that you know the manager, he says.

You just add that feature and the way they think about it is just, you know, adding that Lego to the existing code and and we're done.

The truth, as we all know, is something like this.

The fear of doing that kind of thing doesn't always happen, usually doesn't.

But when it does out removing CO, we want to re factor.

It's just, you know, removing that one single line or in CSS just I don't need that rule.

But we all know what happens in the real world.

When I take out that CSS somewhere, some page is gonna break.

Yeah, re factoring I really want to re factor.

I really want a reflector, that JavaScript But I'm afraid this will happen to me.

And it doesn't matter whether our code is a horribly written pile of spaghetti or a wonderfully beautiful, crafted set of loosely coupled modules.

We really fear our own call, which we fear, changing it because changing code may mean breaking the APP and Web developers, as all developers have have discovered, that developer testing or testing, in short removes the need for this manual testing after co changes.

And developer testing is writing code that tests your own code as part of writing the code itself.

So it's not que es automation engineers doing that for you.

It is you doing that for yourselves, and testing abolishes that fear.

It makes that fear mostly go away because you code and then you write the tests for that code and doesn't really matter whether you're writing it before you write the co TT.

These dollar after I don't really care and you know you run those tests and they break and you fix the bogs, et cetera, and it works.

And once you change your code, you just run the tests again and you're done.

Testing abolishes fear that is the most important thing.

Testing abolishes the fear of one's own code.

Well back and developers have been writing tests for quite some time.

They've had that methodology even before the Web.

The methodologies and tooling are mostly established.

There will be working on it for quite a while.

Well, the Web is young in terms of methodologies.

Nobody really knows exactly what it's, but the tooling is almost there.

It's happening for quite sometimes, a lot of mentors and teachers can see Daws just in serials.

Kevin Lamping, Gleb Okamoto, Shy Resnick And there's hopefully including me were slowly building for JavaScript developers, a methodology based on unit testing component and multi component testing.

Using James Dom and things like Cyprus and selenium and Web driver Io.

No tests for you, you don't know and why?

Let's talk about front and JavaScript tests.

字幕リスト動画再生

CSS 用のテストを書くことは可能!噂を信じてはいけない - Gil Tayar｜CSSconf EU 2019 (Writing Tests For CSS Is Possible! Don’t Believe The Rumors - Gil Tayar | CSSconf EU 2019)

stuff

constantly

specific

basically