Testing the figma pattern

Für ein Kundenprojekt im Bereich Microsoft 365 Modern Workplace suchen wir erfahrene Freelancer (m/w/d) mit Schwerpunkt Microsoft Places. Im Mittelpunkt steht die Beratung, Konfiguration und Optimierung einer Microsoft-365-Umgebung zur Unterstützung moderner Hybrid-Workplace-Konzepte. Aufgaben Beratung bei der Einführung und dem Betrieb von Microsoft Places Analyse bestehender Microsoft-365-Umgebungen und Erarbeitung geeigneter Lösungskonzepte Konfiguration von Gebäuden, Stockwerken, Meetingräumen und Arbeitsplätzen Einrichtung und Optimierung von Desk-Booking- und Room-Booking-Szenarien Integration von Microsoft Places in Microsoft Teams, Outlook und Exchange Online Unterstützung bei Lizenzierungsfragen sowie Best-Practice-Empfehlungen Durchführung von Workshops und Know-how-Transfer für Anwender und IT-Teams Unterstützung bei Troubleshooting sowie im laufenden Betrieb Anforderungen Mehrjährige Erfahrung im Microsoft-365-Umfeld Praktische Erfahrung mit Microsoft Places Sehr gute Kenntnisse in Microsoft 365, Microsoft Teams, Exchange Online und Outlook Erfahrung mit Microsoft Entra ID (Azure AD) Kenntnisse moderner Hybrid-Workplace- und Modern-Work-Konzepte Wünschenswerte Kenntnisse Microsoft Teams Premium PowerShell für Microsoft-365-Administration Erfahrung mit Arbeitsplatz- und Raumbuchungslösungen Microsoft-Zertifizierungen im Bereich Modern Workplace oder Microsoft 365 Erfahrung in der Konzeption und Einführung moderner Arbeitsplatzkonzepte Start: asap Dauer: ca 3 Monate mit Option auf + Einsatzort: Remote / nach Absprache Auslastung: Nach Absprache Interesse? Da sich das Projekt aktuell in der Vorbereitungsphase befindet, möchten wir frühzeitig passende Experten kennenlernen. Bitte senden Sie uns an contract (AT) advergy de : CV Verfügbarkeit Stundensatz (Remote / Onsite) Dreizeiler, wieso Sie besonders gut auf das Projekt passen Vielen Dank und liebe Grüße Seda

We are looking for a detail-oriented person who can thoroughly test our online booking system and check how convenient and correct it works. What needs to be done: Completely go through all sections and tabs of the booking system. Check that all pages work correctly. Pay attention to possible errors, shortcomings, inconvenient moments, or anything that can be improved. Compile a list of comments and recommendations for improving this system based on its functions. Booking check: Book a breast augmentation procedure, go through the entire process up to the payment stage, but do not make the payment. Then return to the site and arrange an online consultation booking. When booking the online consultation, a deposit of £20 must be paid. Check that all emails and notifications are received after the booking is made. Deposit payment: The £20 deposit will either be transferred to your bank card after the task is completed or added to the project payment — your choice. Important: Please test only the procedures specified in the task, and upon completion, send a detailed report of all found errors, comments, and suggestions for improvement. https://vvvbeauty.simplybook.it/v2/# Propose a price

We are interested not just in writing individual automated tests, but in building a quality foundation that can be scaled and maintained in the future.What we expect in the first stage a brief audit of the current testing process and testing environment; identification of critical user (UI/E2E) scenarios; recommendations for the automation stack and architecture of the testing project; setting up the project structure for automation; development of ready-made automated tests for critical user scenarios; documentation on launching, maintaining, and further developing the automated tests.Which scenarios we are interested in The first stage covers only the user part of the site: authorization; product catalog; search; product card; cart; checkout; personal account. API, integrations, and testing of the administrative part of Magento are not included in the scope of the project at this stage.What is important Experience specifically with Magento 2, e-commerce, or marketplace projects will be a significant advantage. In your response to the project, please indicate: experience with similar projects; examples of implemented automated tests or cases; which automation stack you recommend and why; what exactly will be included in the first stage of work; what deliverables we will receive after the completion of the first stage; the estimated number of automated tests that will be included in the first stage; the estimated budget and timeline for implementation. We are considering a long-term collaboration. If the first stage is successful, we plan to expand the coverage with automated tests and scale the approach to other e-commerce projects.

We are looking for an experienced QA partner or team to help build a testing process for an e-commerce project on Magento 2. At the first stage, we are interested not just in writing automated tests, but in a comprehensive approach to organizing QA. What needs to be done: conduct an audit of the current testing process; assess risks and identify critical user scenarios; provide recommendations for building the QA process; help determine which scenarios should be tested manually and which should be automated; suggest the optimal technology stack for automation; prepare an automation implementation plan; evaluate timelines, budget, and further support. At the first stage, we are specifically interested in automating user (UI/E2E) scenarios. The main business processes include product catalog, search, product card, cart, order placement, authorization, and user personal account. Experience with Magento 2, e-commerce, or marketplace projects will be a significant advantage. When responding to the project, it will be helpful to mention: experience with Magento 2; examples of similar projects; which automation stack you recommend (Playwright, Cypress, Selenium, etc.) and why; how you usually build the automation implementation process; an approximate approach to estimating work; who will work on the project (QA Lead, Automation QA Engineer, team). We are considering a long-term collaboration. If the first stage is successful, we plan to scale automation to other e-commerce projects.

About the project: We are developing a browser-based Web3 game on the blockchain: an interactive game world with a map, resource mining mechanics, wallet connection, on-chain transactions, and an internal economy. The project is in the active development stage. We are preparing a build for testing key systems before the next phase. Task: Conduct deep functional testing of the build — find and document bugs, vulnerabilities, and bottlenecks. The goal is not to "complete the game," but to break it: identify where the logic fails, where mechanics can be abused, where UX is poor, and where transactions are failing. Responsibilities: Testing wallet connection and functionality, authorization Verification of transactions and payments (on-chain + in-game) Testing game logic: map, mining, drops, interaction with the world Searching for vulnerabilities and abuse/fraud vectors in the economy and balances Load cases: mass actions, rapid clicks, behavior under load Cross-platform testing: PC and mobile browsers Clear documentation of bugs: reproduction steps, expected/actual results, screenshots, environment Requirements (mandatory): Experience in manual functional testing of web applications for at least 1 year Practical experience in Web3 as a user: wallets (MetaMask, Phantom, etc.), transactions, dApps — without this, wallet and on-chain testing is impossible Experience in game testing Understanding of how web applications work: HTTP, REST API, DevTools Ability to systematically search for bugs and describe them clearly Will be a plus: Experience in testing fintech/crypto products or transactions Working with Postman, test networks (testnet), blockchain explorers Familiarity with Solana Conditions: Format: one-time testing, remote Date: 15.07 Payment: negotiable (please specify your rate in the response) In your response, please include: Experience in QA + an example of an interesting/critical bug you found Your experience in Web3: which wallets you use, whether you have tested on-chain transactions Experience in game testing Your rate for this testing