How can you evaluate the quality of your software products?

Is important to know that software quality attributes can be functional and non-functional. Functional quality attributes are related with user requirements and how this requirements was developed. Non-Functional quality atributes are related with how the aplication works while someone is using it. If the application load bewteen pages is fast or not, in how many different devices i can install my aplication and What is the probability of my data be accessed by hackers, all of this exemples represents non-functional quality attributes and this kind of attribute typically needs a specific kind of test. Icould add another one: The process. The more quality there is in the process, the more quality there will be in the final product

we run developper test longevity and soak test to detect memory and handles leaks we test new features running both progression tests and at the same time making sure we introduce no new regressions ... we run automated tests nightly on each CI generated build for regression and a more expansive suite over the weekends ...

Quality assessment helps ensure that your software meets its intended purpose, is reliable, performs well, and is free of defects. There are several approaches and methods you can use to evaluate software quality: - Functional Testing -Non-Functional Testing -Code Review -Regression Testing -Code Coverage Analysis -Usability Testing -Performance Testing -Security Testing -Compatibility Testing -Accessibility Testing -User Acceptance Testing -Automated Testing -Defect Tracking -Feedback and Review -Documentation -Performance monitoring By combining these various approaches and methods, we can comprehensively evaluate the quality of your software products.

I think that the most common error in SQA is negligence with documents, requirements and the knowledge about the project of the product. Sheila Reinerch says that Agile movement, although bring great benefits for software development also bring a carelessness with this knowledge and this point is something that compromises the quality of many projects. I believe that SQA needs to start to take care of the process quality, Tests are a good strategy but there is so much more in the universe that is related with quality and that goes beyond the product. I really believe that when we understand this, we going to see an advance in technology that we never saw it before.

There is some levels of test System test: Happens when we have the whole system (or release) developed and test all parts togueter. In system test is commom use black box testing techniques; Acceptance test: Happens when final users starts to use the system and validate if it meets your expectations. In this level of tests is used black box or experience technicals based. Integration and Unit tests: Are component tests with this difference. Unit test just one component and integration test two or more components and how components relate each other. This kind of tests is common to be done by developers and typically uses white-box tests.

Deming, author of PDCA, says that the quality of the product depends of the quality of the process and that issued product is a results of a bad process. PDCA exists and is used in engeering for years to care about the process quality. Is sad don't see the same thing in softwares development industries. I really believe that QA can to more for quality than just execute tests. I believe in a QA that don't analyse just the product mas also the process.