I haven’t updated this series in about ten days.
Recently has been updating the interface test platform series, every day there are many fans to friendly bao Good li anti Cui feed geng
So let’s talk about the diary of test development today…
The last few days in support of a dot test mission, a new mall. This isn’t the first version, it’s even been running online for a while, but this time it’s just adding a little feature. I thought it would be done in minutes, but when I saw the schedule for half a month, I knew it wasn’t that easy
On the first day, I tested without even bothering to read the requirements document. Within 2 hours, I found 20 or 30 bugs. I was shocked.
Product sister found that I did not see the document, I use my years of high-end tearing X experience reply: know why I do not see the document? Since I was a fresh blood infusion to the project, I controlled my thinking in order to avoid being preconceived by the product documentation. Therefore, I need to feel the product as an ordinary user. If I find something inconsistent with my usage habits and logic, I will look at the document then. If the document is consistent with my idea, then I have found a bug. After all, the product documentation is strictly a static testing process that we tested, and since it’s not here, my first round of non-documentation testing is just as good as testing your product documentation’s shortcomings.
Secondly, if I can’t understand how to buy things in this mall, I need the help of documentation to understand. There’s something wrong with the product design, because online users don’t study your documents before they use the store. For ISO9126, your ease of use within the easy to understand, easy to use, easy to learn and so on May have problems, so how to test it, it must be a completely did not accept your product documentation preconceived new to test. And the time is tight, I see your documents have to take a long time, it is better to directly test, we test training that year a tour de force is to do not look at the document, directly to the interface to write use cases. I mean, this is one shot at a time.
And then… After my long argument, the room was silent. I then highlighted over 30 bugs, most of which were already online and missed. Why did I see it so quickly, because I didn’t read the document, and it’s very valuable to use this kind of strong results-oriented thinking to justify my point above.
Finally witty as I, successfully resolved a crisis of trust.
Of course, it is recommended that test partners do not imitate me, because they will be easily humiliated by products and development if they are not skilled enough.
In recent days, the company has conducted a promotion defense, presumably the audience gentlemen more or less their own or friends of the company are doing this, every year 1-2 times, is this time point. Our company is no exception. I was surprised, I didn’t know what to do, I was told to do a POWERPOINT presentation, and then I went to the defense. The result is that my powerpoint has no pictures, it’s full of words. And then I’m gonna read it for the board.
Due to the impact of the epidemic, the success rate of companies’ defense has also plummeted. And for me with a higher rank, to be honest, this time the probability of success is slim, and even infinitely close to 0.
Thought anyway also can’t succeed, but also with other departments such as algorithm, architecture of the top big man PK grab a limited number of places, I go to expand knowledge can.
Unexpectedly, it was this relaxed mental preparation that made me talk a lot in the defense process, with active thinking and explosive atmosphere. Forgot all about the 8 VPS and HRBP directors. Then seriously timeout…..
For whether overtime this matter, in fact, there are pros and cons, the drawback is that it will deduct points. Interest is whether you can sacrifice the points you lose. Show more bonus skills in the extra few minutes. You end up adding more. This is a dangerous job. Forty-five minutes are up, and you feel like you’re not scoring enough points to be eliminated. You can go out on a limb and talk about more exciting technologies and future ideas.
The so-called riches and honour risk, or be buckled light, or add high points.
As a result, I asked for dinner, and the next respondent was scheduled for the next morning.
Fortunately, the third day of the time, the notice arrived, promotion success……
After that, we are going to publish an article on techniques for testing development promotion.
Back to business: Recently there was a big demand for apps to bury automated testing.
In your UI automation, you should include automatic scripts that can test the content of HTTP requests sent by your app. We use Charles Postman and other tools for manual testing to capture packages. But how do you automate packet capture and assertion? I have a solution for that. So when the developers came to me with this requirement, I said yes, it was a big job, both in terms of technology and volume. And so on after the opportunity to give you a buried point automation test technical article. Looking forward to? Bonus for promotion ~ okR’s powerful task oh ~
Welcome to continue to pay attention to the interface test platform code development tutorial, some friends feedback that it is a little behind, I will make corresponding adjustments later. Looking at the latest reading volume did not break a hundred, I think may indeed content output a little fast…. Follow suit, this is the threshold of test development, but also the exit card for future testing.
Finally, welcome to share the spread, (in other large groups to share when remember to run after loading X is the most exciting)