Netizens QA

Transcript

1. Netizens Quality Standards 2018
2. Agenda § General information § Standards § Testing § Example
3. General information about QA
4. „ Q&A is not only testing, it’s a process that starts at the very begginnig of the project. The team must understand and remember this fact - it’s crucial to succeed. Seweryn Stroiński Production Director
5. Project Manager is responsible for organizing The process The team must be well informed Proper tools must be used Key elements: § Leader § Stable team § Communication! § Rules and tools
6. Project’s magic triangle Range Time Money Quality You can’t change only the budget or the timeline or the range without changing other elements You should choose two J Quality requires TIME!
7. Our standards
8. Basic documents Defines: § The project and its purpose § The actors § Use cases § Functional requirements § Non-functional requirements Specification
9. Basic documents Defines: § Range of tests § Use cases with examples § Reports § Testing tools Testing scenarios
10. Security OWASP Top Ten § The Open Web Application Security Project - community which creates methodologies, documentation and tools in the field of web application security § Target: protecting applications against most common types of attacks
11. Supported systems & browsers 11 range 96%
12. 1920 x 1080 Most common resolutions 320 x 480 range 98%
13. Our devices Smartphones § iPhone 6 § iPhone 5 § iPhone 4 § Samsung Galaxy S7 § Samsung Galaxy S6 § Samsung Galaxy J5 § Samsung Galaxy A5 § Nexus 5X § Nexus 5 § Huawei P8 Tablets § iPad 3 § iPad mini 2 § Samsung Galaxy Tab S2 § Samsung Galaxy Tab E § Lenovo Idea Tab A2107A And more…
14. Tools we use Redmine Bug Tracker § Main tool for bug tracking § Main tool for communication in testing phase § Available for our clients and developers § Tasks are managed by Project Manager § Every resolved task must be double-checked
15. Testing
16. Small Medium Big Functional P P P Unit tests P P Security P P P Performance P P P Acceptance P P P Tests Project
17. Functional testing Manual Automated
18. Unit tests § Test Driven Development § Unit testing
19. Security testing § Security scanners (Nikto2) § We cooperate with Intracare company which specialises in security tests § Open Web Application Security Project Testing Guide § OWASP Application Security Verification Standard § The Penetration Testing Execution Standard (PTES) § The Open Source Security Testing Methodology § Manual (OSSTMM) § Standard of Good Practice
20. Performance testing § Build scallable application code architecture § High performance TCP/HTTP Load Balancers (HAProxy) § Database scalling (MariaDB Galera Cluster) § Scalable frameworks for realtime apps (NodeJS / Socketcluster.io)
21. Acceptance testing § Target: to determine if the requirements of a product are met § Involve the client § Based on measureable acceptance criteria § Acceptance checklist P
22. External services
23. „ A fundamental problem with software testing is that testing under all combinations of inputs and preconditions (initial state) is not feasible, even with a simple product. constant support software updates
24. Testing - methodology Planning Scenarios Reports
25. Example – wsipnet.pl
26. WSiPnet - timeline 2014.10 2015.11 Testings UX Testings Stage I Testings Stage II Testings Stage III Testings Stage IV Testings Stage V X XI XII I II III IV V VI VII VIII IX X XI Security and performance testing Final testing Functional testing LAUNCH! Testings RWD Testings Stage VIII
27. WSiPnet 4646 hours of pure work
28. WSiPnet - documents Specification Timeline Scenarios & reports Performance
29. WSiPnet - Specification § Target, definitions, actors § Use cases § Business environment § Functional and non-functional requirements § Browsers support
30. WSiPnet - Timeline
31. WSiPnet – Scenarios and reports § Use cases § Reports § Testing scenarios for Responsive Web Design
32. WSiPnet – Performance testing § Page load times § Server response times § 1900 pupils’ accounts § 96 teachers’ accounts § 4 directors’ accounts