Hello, everybody. I'm Rafaela, and I'm gonna share a bit of my experience with end-to-end tests for Web3 applications. So just a bit about me. I have 15 years experience in QA, test automation, test strategy, architecture, and leadership, and I got really passionate about the QA area, so I created this blog in 2011 where, you know, you can find everything that I have learned in the past couple of years.
So code snippets, programming, DevOps, leadership, and test automation, of course. I was born and raised in Brazil, to be more specific, I'm from a coastal city called Santos in Sao Paulo. And you can see the picture on the screen. I'm also a really big fan of Harry Potter, as you can see, and this is one of the reasons why I moved to London eight years ago. And the weather as well, but nobody believed when I said that.
But yeah, the agenda is going to be this one. We are going to talk about what is Web3, then the architecture of the Web3 application, some introduction about the entry-in tests, and the challenge, then the tools that you can use, and we are going to have two demos, one just using a mock, and another one using a framework called SyncPress. And then in the end, we are going to talk about the tradeoffs of each approach.
So what is Web3? Web3 is just a new version of the web. We are on Web2 right now and this Web3 comes with the ideas of decentralization, token-based economics and also blockchain technology. So it offers a read-write-own model, so people, they have financial stake and more power over the online communities they belong to. So they own the data, which is not the case right now. The online experience is expected to change as cell phones and smartphones and the pieces they did in the past, so it's going to be a big change for, you know, us that we are living in this moment.
Some business they try to join this new market but they encounter some pushbacks as you know with blockchain as well. Like, you know, the negative impact on the environment and the financial speculation as well. This is the evolution of the web. So from the first version to now, so the first version we had the static read-only pages where you couldn't interact too much with them. And then now what we have is a bit more dynamic and interactive so we can go there and post things. So, you know, Twitter, we can just send our data away basically through these big corporations. And the Web3, which is the one coming now, is more private, secure and decentralized. So the idea is, you know, our data is not going to be owned by these big corporations but by yourself.
And the architecture of the Web3 is also quite different because it's based on smart contracts like blockchain. So if we see now what we have is basically the front-end, back-end database inside of this web server. And this is controlled by, you know, the corporation or the company, somebody. And the Web3, we have just the front-end in the web server. So this is going to still be part of the, you know, it's going to be controlled by the company or the corporation.
Comments