QA Rules

Software life cycle in terms of QA
___________________________

💥Hello everyone! 💥

⚙️Today we will talk about how the software lifecycle looks like from the point of view of QA

You can argue for a long time that there are different software delivery models, such as waterfall, increment, and others.


🔧But for testing, it is not so important which model is used by the team, because there is a basic rule that applies to almost any model: testing should be included in participation as early as possible.


🗂 It is clear that due to the specifics of the project, at the early stages of developing a feature, it may not be available to the team due to NDA, but these are rare cases, in most cases, testing should start as soon as the feature begins to be developed - at the stage of ideas or requirements.

✏️Because the sooner a feature is considered by a QA specialist, the cheaper it will be to fix bugs. This can be called the “cost of fixing a bug”, the further a feature goes in the development cycle, the more expensive it is to fix emerging bugs, but what if the bug is in the feature’s business logic itself? - then the cost will be simply colossal (but still lower than if the bug is found already in production)

🖥 Do not think that if there is a designer, then there is no point in testing the design - there is, very often possible behavior bugs are caught at this stage

Thus, no matter what model the team uses, testing should be included at every stage of the software life cycle.

For example, a graph from the report of the National Institute of Standards and Technology (NIST) helps to visualize the comparative cost of fixing the same bug at different stages of development

What tools are needed to start QA work
______________________________________________________

💥Hello everyone! 💥

➡️ Today we will talk about what tools are needed for start working as QA

❗️The important point is the set of programs will depends on what we will testing: web testing and mobile testing are different.
Therefore, now I will talk about the most basic programs that will be used in almost any project.

1️⃣ DevTools
The first thing that any QA will require is the ability to work with the developer panel: DevTools
In Chrome, to open the developer panel, just press F12
We can talk about the panel for a long time, because it contains a lot of useful functionality.
But if you take what is useful at the beginning of the study, these are, of course Console, Elements, Network tabs.

2️⃣ Postman
The next important tool is Postman. It allows you to manually (and if there is a strong desire - automatically) send requests (mainly to the server under test) with such a set of fields and parameters that we need, and also view the received response.
The simplest example that can be given is to send a GET request with the address of the current page.

3️⃣ Fork / GitExtensions
The third tool that I recommend to learn is the interface for git. For macos I can recommend Fork, but for Windows I like GitExtensions better.
In general, the purpose of this tool is to provide a convenient interface for working with the version control system, in other words, you will have right in front of your eyes commits, branches, their authors, you will be able to quickly and conveniently navigate through them, switch. Of course, this tool will not completely replace the console git, but it will still be enough to start.

❓For those who already work or have worked in QA, the question is: what tools would you recommend learning for yourself at the start of your career?

💥Hello everyone!💥

👻 It's time to dispel the fog, tell about this channel: what will happen here, what to expect, what are the goals and plans for it.

❓So what will be on the channel:

1️⃣Of course, useful utilities: how to write a test, what is this test plan of yours, how to effectively apply testing on a project, why autotests are needed and how to write them, how to download software and hard skills

2️⃣News from the QA-side of things: these are new technologies and best practices that you should definitely use in your work, or just interesting features that may find a place in your daily work

3️⃣Tutorials: More in-depth articles on in-demand topics

4️⃣My thoughts on QA in general

🗓Goals and plans .. yes, in fact, I just like to see how my work brings benefits, how people improve and grow professionally, I wanted to start sharing with a wider number of people, because more than once I have encountered the fact that not everyone understands what is the main role and purpose of QA in the team and what it should be.