And again about softwate development life cycle

System testing of software is the black box testing conducted on a complete and fully integrated software product based on the software requirements specification. In main focus of this testing is to evaluate Business, Functional and End-user requirements implementation. In Software Development Life Cycle the System Testing performs as the first level of testing where the application is tested as a whole in environment that particularly resembles the effective production environment in order to check if developed software meets functional requirements and to test, validate and verify both the Application Architecture and Business requirements. Basically this is the full end to end testing on the software on the similar to production environment. System Testing preparation procedure: Write/Update System Test Plan based on project plan, test strategy & main test plan Create/Update test cases covering all functional, non-functional, technical & UI requirements and ...

In recent years it is becoming less and less companies where you can meet dedicated test teams working with different development teams under the same product. This is most likely due to financial reasons because there are not so many companies who can afford to keep a team dedicated exclusively to testing and everything related to it. Nowadays a majority of software development companies work using Agile & Scrum, where all team members (software engineers, architects, programmers, analysts, QA experts, testers and etc.) are sitting together and doing their best to meet the goals of the sprint. In such projects testers, in principle, may know nothing about work of their colleagues from other teams because their areas of responsibilities intersect not very often or do not intersect at all. It can work fine until we are not starting talking about organizing automation testing and everything related to it: planning, design, implementation of frameworks and tests, support. I ...

Why do you write automated tests? Many people say "to find bugs" but it is not true. Tests are not looking for bugs. They just verify correspondence of actual and expected results. - So? Where is the “looking for bugs” here? -No, I haven’t seen. Some time ago I had a conversation about unit and integration tests with one of our developers. In the result we've come to conclusion that they are writing tests to verify contracts between components for convenience, access, usage of the defined data types and some other aspects. When you are writing a new code the test will be your first client. If it is easy and comfortable it means that everything is fine.When you are writing test on existing code but facing issues all the time and have to write a lot of workarounds it means that existent code is crap and it requires improving it. The same is applicable for other automation tests written by testers. You are writing them on the framework which works with the application...