What does QA stand for? <\/a><\/p>\n\n\n\nWhy is Quality Assurance so important, and what stages do our QA experts go through in their work? We\u2019ve met with one of our leading QA engineers for the answers. <\/p>\n\n\n\n
The Quality Assurance process at GetDevDone: Questions & answers <\/h2>\n\n\n\n When does the testing stage begin, and what\u2019s the QA department\u2019s primary objective? <\/strong><\/p>\n\n\n\nWe get down to business as soon as <\/strong>a client gives us their approval to start working on their project. <\/p>\n\n\n\nAt the project estimation stage, <\/strong>we review the project specifications (if available), test them for contradictory requirements and feasibility, and suggest the best ways to implement certain modules and features. We also draw a test plan. <\/p>\n\n\n\nIf we have received no project specs from the client, a QA writes the project specifications and summary jointly with the developers. Thus, the testing process gets underway already at the project estimation stage. <\/p>\n\n\n\n
We must anticipate <\/strong>problems that our clients may encounter. We also ensure that everything looks and functions exactly as the client has specified by referring to the final quality assurance website checklist. <\/p>\n\n\n\nWhat main stages does the testing process include? <\/strong><\/p>\n\n\n\nHere is the typical sequence of steps<\/strong> we go through while testing every<\/strong> project: <\/p>\n\n\n\n\nFirst of all, we test the project specifications<\/strong>. <\/li>\n\n\n\nWe estimate the project complexity level. <\/strong>If the project is not very complicated, we use our standard test plan. Otherwise, we supplement this standard plan with additional test activities in accordance with the project specifics. <\/li>\n\n\n\nWe perform module testing. <\/strong>That speeds up the testing process considerably. As soon as one module has been developed, it immediately gets tested and is shown to the client. Later, when the entire project is finished, we move on to acceptance testing. <\/strong>Every module goes through a routine testing cycle when we run standard test cases. Every bug gets fixed straight away followed by regression testing. <\/strong> <\/li>\n\n\n\nAt every testing stage (module, system, or acceptance), we perform functional <\/strong>and non-functional<\/strong> testing. The non-functional <\/strong>testing phase includes the following: <\/li>\n<\/ol>\n\n\n\n\nUsability testing<\/strong>. We test how easily a user can edit the modules via the admin panel, how intuitive the website navigation is, and so on. Our principal goal is to simulate any actions that a real user may perform both on a desktop computer and a mobile device. A website interface must be clean and straightforward. Anyone should find it simple to move around, whether they see it for the first time or are going to work with it regularly. <\/li>\n\n\n\nSecurity testing. <\/strong>This activity is particularly important if the modules have been built by our developers. <\/li>\n\n\n\nInstallation\/portability testing.<\/strong> We test the project in the required server environment, including the PHP version, CMS, framework, plugins, and hosting setup specified for the project. When needed, we also test the project on the client\u2019s own server to catch environment-specific issues before delivery. <\/li>\n\n\n\nMarkup validation against the World Wide Web Consortium (W3C) Standards.<\/strong> The goal is to make sure the markup contains no critical HTML or CSS syntax errors. Our developers and website quality assurance experts strictly follow all of the W3C coding specifications. That guarantees that a design will render correctly in all browsers. <\/li>\n\n\n\nGraphical testing.<\/strong> We verify that a page or website corresponds exactly to your design. Our work is always pixel-perfect. However, we can be flexible under certain circumstances. For instance, if we\u2019ve noticed an inaccuracy in your design, such as different offset values in different headings, we may decide not to follow the design to the letter and correct those mistakes in the markup.<\/li>\n<\/ul>\n\n\n\nThis is what the functional testing <\/strong>phase includes: <\/p>\n\n\n\n\nVerification<\/strong> that the specified features and all of the client\u2019s requirements have been implemented the right way. The website QA\/testing procedure suggests that no button or gallery is skipped. We check all forms, fill in all fields, register in all forms, and go over all the user\u2019s steps without exception. We search for and fix critical bugs: <\/li>\n<\/ul>\n\n\n\n\u2718A page isn\u2019t displayed correctly<\/p>\n\n\n\n
\u2718A developer hasn\u2019t implemented some of the features<\/p>\n\n\n\n
\u2718Certain code in the project fails to work<\/p>\n\n\n\n
At this stage, we apply two testing techniques: <\/strong><\/p>\n\n\n\n\nPositive testing <\/em>(we expect a feature to work correctly). We imitate a user\u2019s logical route around one page or the entire website from start to finish. <\/li>\n\n\n\nNegative testing <\/em>(for example, what will happen if we press two buttons at the same time, enter invalid data into a form, and so on). Those actions are not related to a user\u2019s logical route around a website. <\/li>\n\n\n\nCross-browser and multiple-device testing<\/strong>. Our QA engineers constantly track updates for various browsers to know their latest modifications. We test every markup and page created for a specific CMS in the latest versions of the most popular web browsers and mobile operating systems. <\/li>\n<\/ul>\n\n\n\nWe can also test a project in earlier browser versions<\/strong> for an extra fee.<\/p>\n\n\n\nIf the project is a multilingual resource, our website quality assurance checklist also includes localization testing. <\/strong>We verify the correct translation of every available field both on the back-end and front-end. <\/p>\n\n\n\nIf the client chooses the \u201coptimized for load speed\u201d option, we conduct performance testing<\/strong> as well by checking how fast web pages can load. <\/p>\n\n\n\nFinally, after we\u2019ve completed the regression testing and our developers have fixed all the bugs, we perform smoke testing<\/strong> to make sure the main features work as they should. Only when all is perfect are we ready to deliver the end product to the client. <\/p>\n\n\n\nDo you perform testing on real gadgets? Why is device testing so important? <\/strong><\/p>\n\n\n\nYes, we perform testing on a multitude of real devices. That\u2019s what distinguishes GetDevDone from freelance developers who have limited capabilities and can test projects on one or two gadgets most of the time. <\/p>\n\n\n\nHere are the key benefits of real-device testing:<\/strong><\/p>\n\n\n\n\nWe can verify the correct functioning of a website or page on a real device in compliance with the client\u2019s requirements. <\/li>\n\n\n\n We can verify the proper functioning of a website or page in a mobile browser, which is different from its desktop version. <\/li>\n\n\n\n We can check that the solutions used on a website are compatible with the device\u2019s hardware and software. <\/li>\n\n\n\n We can change the device\u2019s orientation (vertical or horizontal) to see how a page reacts to animations and the rearrangement of user interface elements. You can use emulators for the same purpose. Sometimes, however, emulators can\u2019t reproduce the problems that users encounter on real devices. It\u2019s only on real devices that we can test the native behavior of a website\/app. No emulator is capable of that. <\/li>\n\n\n\n We can test typing text by means of the device\u2019s virtual keyboard. <\/li>\n<\/ol>\n\n\n\nWhen do you fix bugs? <\/strong><\/p>\n\n\n\nTo exceed our clients\u2019 expectations and deliver their projects as promptly as possible, testing and bugfixing at GetDevDone are simultaneous processes. Regardless of the project’s deadline, our website quality assurance experts always <\/strong>perform testing. Therefore, the more time we have, the deeper and broader test coverage we can provide. <\/p>\n\n\n\nDo you perform automated testing? <\/strong><\/p>\n\n\n\nOur QA engineers test each project based on our clients\u2019 specific requirements. That\u2019s why we perform manual testing at every stage of the QA process. That being said, the larger the project is and the more time we need to spend getting it done, the more acute is the need for automated testing. Whenever necessary, we write automated tests to cover all the functionality. <\/p>\n\n\n\n
Wrapping Up<\/h2>\n\n\n\n We hope that you now have a good idea about how we test projects at GetDevDone. Our website quality assurance specialists are trained to maintain the highest quality standards. Each page is manually tested on a variety of real devices and in multiple browsers, while bugs are fixed the moment they are discovered. Do you have any suggestions or ideas for our QA professionals? Get in touch<\/a> with us.<\/p>\n\n\n\n\r\n \r\n <\/div>\r\n
![\"Our](\"https:\/\/s3.amazonaws.com\/newblog.psd2html.com\/wp-content\/uploads\/2020\/02\/14192143\/QA_process.png\")
<\/figure>\n\n\n\n![\"Non-functional](\"https:\/\/s3.amazonaws.com\/newblog.psd2html.com\/wp-content\/uploads\/2020\/02\/14191319\/Non-Functional_testing.png\")
<\/figure>\n\n\n\n![\"Functional](\"https:\/\/s3.amazonaws.com\/newblog.psd2html.com\/wp-content\/uploads\/2020\/02\/14191406\/Functional_testing.png\")
<\/figure>\n\n\n\n![\"Real-device](\"https:\/\/s3.amazonaws.com\/newblog.psd2html.com\/wp-content\/uploads\/2020\/02\/14191857\/benefits-1024x498.png\")
<\/figure>\n\n\n\n![\"decor\"](\"https:\/\/s3.amazonaws.com\/newblog.psd2html.com\/wp-content\/uploads\/2024\/02\/20151935\/Banner-1.png\")
<\/div>\r\n