FAQ – SnoopGame QA

[https://snoopgame.com/] FAQ Competence QA Services Service Models Testing Types Process Docs Tools Testimonials Our Story Contact us mobile menu switcher FAQ Competence QA Services Service Models Testing Types Process Docs Tools Testimonials Our Story Contact us ✅ What is essential to start? 1> Platforms for the upcoming test. iOS, Android, Amazon, macOS, Windows, VR/AR, all together or separately; 2> Builds and where to find them. TestFlight / HockeyApp / Google Beta / Steam Key or a package copy .apk/.ipa/.exe; 3> Aim of the current test iteration. For example, “Focus on the Q1 event questline – specification attached.”; 4> Deadlines for task execution. Starting when you ready and finishing when you need it done; 5> Reports , their frequency, and format. Daily, weekly, upon completion of the task; 6> Documentation , if there is any available. Our team is able to develop any test documentation you might need to use; 7> Bug tracking system . JIRA, Redmine, Asana, HacknPlan, Trello, Google Sheets, uTrack, etc – anything your team is comfortable with; 8> A place to communicate . Slack, Skype, Discord, Telegram, etc. + a person who knows the project to determine expected results; 9> Cheat menu and/or test accounts. To speed up progression without disrupting the system. We could also offer recommendations on creating it; X> The invoicing process . Per task, per sprint, weekly, monthly. SWIFT payments are preferable. The requisites will be indicated in the Agreement; 📲 Do you have devices/platforms we need? Our strategy is to provide maximum testing coverage within a shortest possible timespan. Thus our device park is optimized for this task. + we are able to acquire any additional hardware upon your request. ⏰ How do you calculate the testing time? We provide a free project evaluation on any stage of development. After studying the builds, docs and requirements we will provide you with a custom test plan draft. You can then study it with your team and negotiate any details, as we will represent QA tasks in the form of precise hourly blocks. 💰 What is the usual quote? Testing a mobile game is bidding between 500 and 4000 USD. 🐞 What bug tracking system you use? We prefer Jira but also worked with Asana, Mantis, Redmine, Bugzilla, HacknPlan, Trello, Google Docs and MS Excel. 🔎 What types of test activities do you provide? – Development and execution of test scenarios; – General test planning and requirements analysis; – Documenting found defects in the bug-tracking system; – Analyzing and visualizing the results obtained during testing; – Providing reports on product quality in one or several iterations depending on the size and complexity of the project. 📌 Is there are any guarantees for provided QA? If the specification does not reflect the true quality requirements, the product’s quality cannot be guaranteed. Nevertheless, we are able to prepare test kits that guarantee covering all aspects and expected results within the application. In addition, we can offer product support on release. Our QA specialist will monitor users’ reviews to create bug reports, so the development team could fix them at once. 🐕 Why did you name your company SnoopGame? We thought it sounds fitting for a Quality Assurance company. snoop [snuːp] (spy, search) – to look around a place secretly, in order to discover things or find out information about someone or something; It’s a pretty valid description for our work – we snoop the bugs out of your product. 📅 When the time is right for a QA? Testing could be useful in all stages of the project life cycle, but generally – sooner, the better. ⌛️ How often do I need to test my project? That depends on your development cycle and amount of content in each update. Could be ranging from testing several updates per week to one test run per month. 💎 Will the project become perfect after testing and debugging? After the round of testing and debugging, we can verify that the project meets all of the requirements and quality criteria. The project is “perfect” in terms of QA when it processes any user input in any given environment without unexpected behavior. 🕵 How many testers do I need in a QA team? It strongly depends on the project complexity and the frequency of updates. For a project like C.A.T.S. – on a second year after the release it’s best to have a 4-6 full-time QA’s And we also throw 6 more QA’s to execute periodic extensive testing of new updates in a matter of days before the release. – If you need to run basic testing for 120 hours in 5 days – a team of 3 will do; – If your plan is to cover 400 hours of testing in two iterations, 5 days each – a team of 5 QA’s will be enough; – If the schedule is tight and the scope is 1 280 hours per month – up to 8 testers on a full-time basis will be needed. 👥 Who will be involved in testing my project? Each new task will be handled by top-performing QA with sufficient qualifications to manage the project. We rarely switch Project Leads, so knowledge will be accumulated by the team throughout the testing period. The team will be able to deliver its top expertise after a few iterations when they get to know the project better. SnoopGame QA is 44 testers in 4 teams, from Trainee to Senior and the Head of QA who oversees the workload distribution. Don’t forget the Accounting, Office Management, System Administration, Business Development, SMM, HR, and Cleaning staff. 💢 Didn’t find the answer you need? Submit a question to our experts: faq@snoopgame.net Your next great test awaits: LinkedIn Facebook Clutch D-rush C-base QAList DOU Copyright © 2015 – 2020 LLC Snoop Game. All rights reserved. Icons designed by Freepik from Flaticon Privacy Policy We are glad to know what you think: * Your Name: * Contact Email: Please leave your feedback below: Attach your best photo SEND REVIEW close popup Apple iOS 8+, 9+, 10+, 11+; 12+; 13+; iPhone 4S, 5, 5S, 5C, 6, 6+, 6s, 7, X; iPad Air, Air 2, mini, mini 2, mini 3, mini 4, Pro 9.7″ macOS: 10.10 Yosemite 10.11 El Capitan 10.12 Sierra 10.13 High Sierra 10.14 Mojave MacBook Pro MacBook Air iMac Mac mini PC: AMD Radeon R5, R7, RX480 Nvidia GeForce GT 710, GTX 550 Ti, GTX 650 Ti, GTX 980 Ti, GTX 1050, GTX 1060, GTX 1080 Ti Intel Core i5, i7 AMD FX, A4, A6, A8, A10, Ryzen 3, 5 4, 8, 16 GB 16:9, 16:10, 21:9 HD, FullHD, 2K, 4K Windows 7, 8, 8.1, 10, 10 Mobile ARM, x86, x64 Linux: Debian 9.5 Ubuntu 18.10 VR: PS VR HTC Vive Oculus Rift Consoles: Xbox One (UWP) (XDK in Q1 2020) TestKit – PS4/PS4 Pro (from Q1 2020) Nintendo Switch (check availability switch @snoopgame.net ) Android Devices: Screens 800×480, 960×540 1024×600, 1280×800 1280×720, 1440×720 1520×720, 1920×1080 1920×1200, 2560×1440 2048×1536, 2560×1600 3840×2160 CPU’s Qualcomm Snapdragon Samsung Exynos Cortex A-Series NVIDIA Tegra Intel Atom MediaTek GPU’s NVIDIA Kepler PowerVR Vivante Adreno Mali Android Versions: Jelly Bean (4.1 – 4.3) Kitkat (4.4.1 – 4.4.4) Lollipop (5.0 – 5.1) Marshmallow (6.0+) Nougat (7.0+) Oreo (8.0+) Pie (9.0+) Q (10.0+) R (11.0+) Mobile VR: Samsung Gear VR Google Cardboard Various Smart TV’s close popup Functional Testing Functional testing is aimed at verification of functional requirements implementation. Our team will perform complex testing and find problems before your customers will encounter them. By studying requirements and specifications, we prepare a set of scenarios and test cases. You will receive a full report at the end of the task. Types of Functional testing are: Unit Testing, Smoke Testing, Sanity Testing, White/Black box Testing, User Acceptance Testing. close popup Compatibility testing We will check whether your software is capable of running on different hardware, operating systems, applications, network environments or mobile devices. It’s basically a check of how well a system performs in a particular environment. Types of Compatibility testing are: Backward/Forward compatibility, Operating Systems, Hardware, Software, Network, Browser, Devices, Mobile. close popup Load and Performance testing We use it to determine how fast system performs under a particular workload. It can serve different purposes like it can demonstrate that the system meets performance criteria. We can compare two systems to find which performs better. Or it can measure what part of the system or workload causes the system to perform badly. Why to do performance testing: To Identify bottlenecks such as database configuration, To Determine if a new release is ready for production, To Gather metrics useful for tuning the system, To Improve user experience, To Increase revenue. close popup UX and Usability testing Usability testing reveals whether users feel comfortable with your application according to different parameters – the flow, navigation and layout, speed and content – especially in comparison to prior or similar applications. Usability testing includes the following five components: Memorability; Learnability; Satisfaction; Efficiency; Errors. close popup Security testing We check if the application is vulnerable to attacks, if anyone hack the system or login to the application without any authorization. It is a process to determine that an information system protects data and maintains functionality as intended. Non-repudiation, Confidentiality, Authentication, Authorization, Availability, Integrity. close popup Regression testing When any modifications are done to the application code it can bring unexpected issues. It is very important to test whether the existing functionality is intact. Regression helps in maintaining the quality of the product along with the new changes. Regression testing is used when: Any performance related issue is fixed, Any new feature is added, Any enhancement is done, Any bug is fixed. close popup Compliance testing We will evaluate your project compliance with the guidelines of the specific platform – Apple, Google, Amazon, Microsoft, Sony, Nintendo, etc. ur team will pinpoint any drawbacks in standards implementation. It’s basically an audit of a system carried out against known criteria. Benefits of Compliance Testing: Provides appropriate utilization of standards, Assures the proper implementation of specifications, Assures that interfaces and functions are working as expected. close popup Requirements and Documentation testing We go through the Requirement document in order to identify the testable requirements. Activities to be done in Requirement analysis phase: Identifying the testing techniques and testing types, Analyzing the System Requirement Specifications, Preparation of Requirement Traceability Matrix, Identifying the testing environment, Prioritizing the features testing. close popup We use cookies to ensure your breathtaking experience on our website. ✅ Accept? OK 🍪 Reject ❌ Revoke cookies 🕳