Front-end entertainment

It’s been a bit of a buzz at the front end these days.

Github brush volume, Vue rip X, version angularJs…

Want to mix front end, in addition to have enough strong learning force.

You have to have a roller coaster heart.

Public cook’s pot is your pot

Once argued with the leadership in the meeting.

Leader says:

“All test bugs should be assigned to the front end first, and then pointed out to the parties after the front end finds out the cause.”

This is when the tester manually tests the interaction process

Encounter can not login, pictures do not show, purchase is not successful, click no response and so on unified to the front end

Interestingly, from the perspective of the project, this seems to be right and acceptable.

Standing in front of the Angle, is a completely politically correct backdog.

However, the so-called correct, the so-called reasonable, the so-called process is a prerequisite.

They want the horses to run but not eat grass. They want employees to work overtime but not pay overtime.

So, the front end, as the performance layer of everything, you pot, you back set.

Add a sentence:

The time for locating the bug is not given, and the conditions for locating the bug are generally not given.

You can handle the front end on your own.

The life of a man carrying a cauldron

I don’t know what to say in a few words.

Some bugs test directly modifying the database.

Some bugs are accidental and cannot be repeated.

Some bugs have no conditional retest, such as credit investigation.

Some bugs are simply back end return exceptions.

There are also some bugs that are purely requirements in disguise.

But a process is a process.

You’re gonna have to prove that the pot isn’t really yours before you can move on.

As soon as something goes wrong,

The product looks for you, the UI looks for you, the backstage looks for you, the test looks for you, the boss looks for you

To locate or solve a problem,

You have to find the product, you have to find the UI, you have to find the backend, you have to find testing, you have to find operations, you have to find…

In other words, the front end just does its job

But also during development

  • Communicate some problems passively

  • Be proactive in locating problems

  • Let the uncooperative cooperate with you

  • Make time to solve some problems

These questions are many, most of them specious.

: : Chettuzai vs Curd

Some front-end states cannot be generalized.

Different companies and different businesses have different situations.

In 9102, the front end was no longer just a cut-out.

But the front end is still not necessarily the core of the company.

Q:

Is your leader back-end or front-end?

Many tongues are small

In the cold of winter, who works overtime, who leaves first?