TASQA Weekly Devlog Update 2024-05-20 About teammates This week, we've welcomed two new engineers to our team. At TASQA, we pride ourselves on bringing in exceptional experts in their fields, with our engineers boasting 4 to 20 years of IT experience. As Steve Jobs said, professionals enjoy working with other professionals. In our team, you'll find only positive and kind individuals, which makes us strong and united. We don't aim to enforce a corporate culture or fit everyone into a single mold—each of us is unique, without labels or rigid rules. What We Achieved This Week: 1. Enhanced URL Handling for Tasks: We've added logic to handle URL-based requests efficiently. If a user accesses a task via its ID, the system now fetches the specific task from the database. This ensures that users get the correct data when navigating through different task IDs. 2. User Retrieval by ID: Implemented functionality to fetch user data by ID for the frontend. Soon, when you visit another user's page, their information is accurately displayed on the frontend. 3. Improved URL Structure for Code Tasks: We've refined the URL structure to include database IDs for code tasks. When a user navigates to a specific code route, such as code/en/662e018232889399270f3390, the system requests the corresponding task from the database. If a user visits code/en/ without an ID, the system dynamically adds the ID from the database response to the URL. 4. Bug Fix in Code Preparation: Addressed a bug where Prettier was adding an extra line to the end of the syntax highlighter. This fix ensures that code examples used for task preparation are clean and accurate. 5. Enhanced User Data Endpoint: Updated the /users endpoint to include registration date, avatar, and nickname. Soon this enhancement supports upcoming features that will allow users to change their avatars, nicknames, passwords, and emails, providing a more personalized user experience. 6. Resource Optimization: Optimized the number of requests using abort controllers to conserve resources and reduce energy consumption. This initiative aligns with our commitment to sustainability and environmental conservation. 7. User Choice and Statistics Tracking: Implemented functionality to record user choices and update statistics. This feature enables users to track their progress and analyze their performance to identify areas for improvement. - Comprehensive User Statistics: We now offer detailed statistics on all user solutions, which will be made publicly available on our main website. This includes both all-time and daily statistics. Thank you for following our journey. We are committed to continual improvement and appreciate your support. Stay tuned for more updates from your TASQA team!
TASQA’s Post
More Relevant Posts
-
TASQA Weekly Devlog Update 2024-06-15 At TASQA, we are dedicated to providing innovative features and services for everyone aspiring to become a top-tier professional in their field. Over the past two weeks, we have focused on fixing bugs, improving user experience, and completing the initial deployment phases. Our team of top specialists is committed to leveraging AI to unlock new opportunities for users. This month, we are excited to roll out a small portion of new features for beta testing, representing only 20-30% of what we plan to introduce to the public. What We Achieved These 2 Weeks: 1. Code Snippet and Question Feature: Implemented a feature that allows engineers to work with code snippets and answer related questions. This addition not only provides theoretical knowledge but also practical skills on our platform for engineers. We have ambitious plans to compete with LeetCode and Codewars, ensuring that rote memorization will no longer be a problem before interviews. 2. Usage Limitation for Unregistered Users: Restricted the service usage for unregistered users after a certain period. It is important for us to track user progress to improve the service and offer the best experience to other users. 3. License Agreements Added: Integrated license agreements into our platform to ensure compliance and clarity for all users. 4. Backend Password Editing: Implemented backend password editing functionality, which will soon be integrated into the frontend. 5. Mobile Device Restrictions: To ensure an exclusively positive user experience, we currently offer our services only on desktop devices. 6. User Dashboard Completion: Finalizing the implementation of the user dashboard. It will be very simple at launch, with more features to be added over time. 7. Branded Emails: Developed branded emails with a unique design to represent TASQA. We take pride in our UI/UX solutions. 8. Interest-Based Topic Selection: Users can now select topics of interest for any profession, enabling more relevant questions, hints, and an improved overall experience. 9. Password Recovery Integration: Integrated password recovery functionality. If you forget your password, recovery is now seamless and efficient. 10. Deployment Optimization: Since June 12th, we have been working extensively on refining the deployment process. It is crucial for us to enhance this process to provide rapid fixes and improvements to our service during both good and challenging times. We are excited about these developments and look forward to continuing our mission of empowering professionals with the best tools and resources. Stay tuned for more updates! With warmest regards, The TASQA Team
To view or add a comment, sign in
-
Founder - DamageBDD - Behavior Verification At Planetary Scale. ⩓ ₿ 🗲 Æ. zap me npub1zmg3gvpasgp3zkgceg62yg8fyhqz9sy3dqt45kkwt60nkctyp9rs9wyppc
Read https://damagebdd.com and explain why it makes sense to use damagebdd for large complex projects with many moving parts moving fast ? DamageBDD is ideal for large, complex projects with many moving parts due to its human-readable Gherkin syntax, facilitating collaboration among team members with varying technical skills. It supports large-scale load testing, continuous regression, and integrates seamlessly with CI/CD workflows. By enabling early detection of performance issues and ensuring applications handle high user traffic, DamageBDD helps maintain project velocity and quality, making it suitable for fast-paced, multifaceted projects. For more details, you can visit [DamageBDD](https://damagebdd.com).
To view or add a comment, sign in
-
Excited to receive the Writing Badge for my blog on mastering the Postman API! 🚀 Sharing insights and tips to streamline API testing and development. Check out the blog here: https://lnkd.in/dy6Y27nz #postmanstudent #postmanapi #apitesting #devcommunity
Mastering API Development and Testing with Postman: A Comprehensive Guide
dev.to
To view or add a comment, sign in
-
Our CTO, Guy Arieli, has penned an intriguing article on Test Automation for The AI Journal, exploring the depths of test automation. A compelling read on 'Things You Didn’t Know About Software Testing and Its Pros and Cons.' Dive into this comprehensive article that demystifies the intricacies of software testing, uncovering not just the advantages but also shedding light on the challenges that come with automation. Whether you're a seasoned professional or just starting out, this piece offers valuable perspectives on enhancing efficiency while navigating the complexities of automated testing. A must-read for anyone looking to stay ahead in the ever-evolving landscape of software development. Check it out! https://lnkd.in/dAv3-hn8 Tal Barmeir
Test automation - things you didn’t know about software testing AND its pros and cons - The AI Journal
https://aijourn.com
To view or add a comment, sign in
-
📊 Are you ready to level up your API testing skills? In our latest blog post, we explore reliable and free API testing playgrounds for handling POST, PUT, and DELETE requests. Here’s a sneak peek at what you’ll learn: - 🌐 **HTTPBin**: An excellent resource for testing different types of HTTP requests. - 🚀 **Postman**: Offers collections and mock servers for user-friendly testing. - 🛠️ **JSONPlaceholder**: A free fake online REST API perfect for prototyping. - 📦 **Restful-API**: Enables data storage for comprehensive testing scenarios. Plus, discover how Repeato can enhance your API testing workflow with its no-code automation solutions! Don’t miss out on these valuable resources! #APITesting #SoftwareDevelopment #QualityAssurance #TechBlog
Finding Free API Testing Playgrounds for POST, PUT, and DELETE Requests - Repeato
https://www.repeato.app
To view or add a comment, sign in
-
📊 Are you ready to level up your API testing skills? In our latest blog post, we explore reliable and free API testing playgrounds for handling POST, PUT, and DELETE requests. Here’s a sneak peek at what you’ll learn: - 🌐 **HTTPBin**: An excellent resource for testing different types of HTTP requests. - 🚀 **Postman**: Offers collections and mock servers for user-friendly testing. - 🛠️ **JSONPlaceholder**: A free fake online REST API perfect for prototyping. - 📦 **Restful-API**: Enables data storage for comprehensive testing scenarios. Plus, discover how Repeato can enhance your API testing workflow with its no-code automation solutions! Don’t miss out on these valuable resources! #APITesting #SoftwareDevelopment #QualityAssurance #TechBlog
Finding Free API Testing Playgrounds for POST, PUT, and DELETE Requests - Repeato
https://www.repeato.app
To view or add a comment, sign in
-
Senior Software Quality Assurance Engineer at iENGINEERING | Manual and Automation | Backend Tester | Database Testing | Jmeter | Postman | Selenium | Healthcare, EHR, ERP |
Master Testing with Postman's Superpowers! APIs: the lifeblood of modern apps, yet testing them can feel like wrangling dragons. Fear not, brave developer! Postman swoops in as your trusty steed, simplifying API testing and making you a dragon-slaying champion. Why Postman Rocks: Intuitive Interface: No more cryptic commands! Postman's friendly UI lets you build and send requests with clicks, not code. Method Master: Unleash the power of GET, POST, PUT, DELETE, and more – all at your fingertips. Dynamic Duo: Craft reusable requests with variables, saving you time and sanity. Data Decoder: JSON and text formatters reveal response secrets in an instant. Scripting Sage: Write JavaScript code to tailor tests and automate complex scenarios. Teamwork Makes the Dream Work: Share and collaborate on tests, ensuring everyone's on the same page. Benefits Galore: Efficiency Unleashed: Automate repetitive tasks and conquer mountains of tests in record time. Accuracy Ace: Catch bugs and performance issues before they wreak havoc on your users. Collaboration Conquers: Share tests and results with your team, building a fortress of quality. Maintenance Made Easy: Organise and manage tests like a pro, keeping them sharp and up-to-date. Ready to Ride the Postman Wave? Download it for free and transform your API testing from a fire-breathing beast to a purring kitten! P.S. Share your API testing battles and Postman victories in the comments below! ⚔️
To view or add a comment, sign in
-
🤖 #NoCodeTools v/s #ToolsWithCode 💻 🚀 Are the No Code/Low Code Testing Tools Ideal for Complex Testing Projects ?? 🚀 The rise of no code/low code testing tools like Katalon, Mabl, TestSigma ... plus the spice of AI on it has transformed the software testing landscape. These tools empower teams to create and execute tests quickly, enabling faster deployment and increased efficiency. They lower the barrier for entry, allowing non-technical users to contribute to the testing process, which can be a game-changer for many organizations. However, while they offer significant advantages, no code tools have limitations, especially for large and complex projects. Here are a few drawbacks: Scalability: As projects grow, maintaining and scaling tests in no code environments can become cumbersome. Customization: Complex applications often require tailored testing scenarios that no code tools may not support adequately. Integration: Larger projects frequently rely on extensive integrations and dependencies, which can be challenging to manage without coding flexibility. Vendor Dependence: Using no code tools means relying on the vendor’s design and limitations. If the platform doesn’t support specific features or changes, teams may find themselves constrained by the vendor's roadmap. For these reasons, many teams still lean towards the warrior tools with coding like Selenium, Cypress, and Playwright. These frameworks provide the necessary depth and control to navigate intricate test cases, ensuring thorough coverage and reliability. In summary, while no code testing tools are excellent for rapid, straightforward projects, when it comes to the intricacies of big, complex applications, the coding route often proves more effective. It's all about choosing the right tool for the right job! 🤞 Let's see who wins the battle in near future. 🤞
To view or add a comment, sign in
-
🎉🎉🎉 RELEASE ANNOUNCEMENT 🎉🎉🎉 Testing with Celery has *never* been so easy! I am glad to announce the release of a completely new plugin for pytest, pytest-celery, that provides E2E testing capabilities for Celery Applications like never before 🤯 This new release has been under my umbrella for about a year, and I am excited to finally share the fruits of my labor with the world! User Manual: https://lnkd.in/eFDUA-kg PyPI: https://lnkd.in/efzENYBy Source: https://lnkd.in/ev6ZHJrQ Can be used for Unit, Integration and Smoke / Production-like testing environments. Install with: pip install -U "pytest-celery[all]" ** Spread the news! ** Key Highlights - Simple: TDD-based design for simple API usage. - Flexible: Highly configurable for even particular cases. - Fast: Fully supports pytest-xdist. - Annotated: IDE autocomplete support for the plugin’s API. Supported Vendors - Brokers: RabbitMQ, Redis - Backends: Redis, Memcached Main Features - Architecture Injection: Allows dynamically injecting architecture components. - Docker-based: Uses Docker behind the scene. - Batteries Included: The plugin provides a set of built-in components that can be used to test ideas quickly. - Code Generation: Mechanism for advanced testing capabilities at runtime. - Isolated Environments: Tests don’t mess up each other, yes, even if you forgot to clean up. - Tests as First-Class Citizens: The plugin is designed to work for you, not the other way around. - Extensible: Following the S.O.L.I.D principles, the plugin uses a plug-and-play design to allow easy replacement of pipeline components.
To view or add a comment, sign in
-
Have you ever found yourself testing code but don’t want to deal with live APIs? Maybe the API isn’t ready, or perhaps it's too slow or expensive to use during testing. That’s where API stubbing and API mocking come into play—but these techniques aren’t exactly the same. In API stubbing, you're basically settting predefined responses for specific API calls. It's like a quick shortcut when you only need static data to move forward. On the other hand, API mocking allows you to simulate the behavior of an API with dynamic responses, imitating real-world conditions without calling the actual API. The key difference? Stubbing is fixed, and mocking is dynamic. Each has its use case, and picking the right one depends on your scenario. I talk more about these techniques in my article on the AmbassadorLabs blog. You can check it out here: https://lnkd.in/dvyk5MnY
API Mocking vs. API Stubbing: Key Differences and Best Use Cases
getambassador.io
To view or add a comment, sign in
7 followers