Worldwide trainers and writers inc

https://lnkd.in/dkxGF97x

https://lnkd.in/didZrERS

chatai describing the menachos from today's rambam.. Mitch Rich Moshe Akselrud ... thoughts?

https://lnkd.in/dMQuPMUe this story won't go away...

Anyone transitioning from Worksoft to Tosca? Here are some strategies to simplify the process: - **Custom Scripting for Partial Automation:** Utilize custom scripts in Python or PowerShell to automate parts of the conversion process, such as migrating test data or converting consistent test steps. - **API Integration:** Use Tosca's API testing capabilities to recreate interactions if your Worksoft Certify scripts interact with APIs. - **Modularization:** Reduce manual work by creating reusable modules for common test steps with Tosca's modular approach. - **Third-Party Consulting:** Consider consulting services specialized in tool migrations to accelerate the process with automated migration scripts and manual adjustments. - **Tool Migration Best Practices:** Prioritize automation, document and plan your scripts to facilitate the manual conversion process. #Worksoft #Tosca #Automation #API #Testing #ToolMigration #BestPractices

hold your horses... doesn't work that well.

**Tosca vs. Eggplant Functional: A Quick Comparison** When choosing between Tosca and Eggplant Functional for test automation, it's essential to consider their unique strengths: 1. **Testing Approach**: - **Tosca**: Uses a model-based approach, allowing scriptless automation. Tests are created by modeling the application, making it ideal for enterprise apps. - **Eggplant Functional**: Relies on image-based testing, interacting with the application as a user would by recognizing UI elements visually. Great for cross-platform testing. 2. **Ease of Use**: - **Tosca**: User-friendly with a graphical interface and minimal coding. However, mastering its model-based method may take time. - **Eggplant**: Intuitive with its image-based approach, using SenseTalk, an easy-to-learn scripting language. Image management may require careful attention. 3. **Supported Platforms**: - **Tosca**: Supports a wide range, including web, mobile, desktop, and enterprise applications like SAP and Salesforce. - **Eggplant**: Tests any GUI-based application across platforms but depends heavily on reliable image recognition. 4. **Test Maintenance**: - **Tosca**: Lower maintenance due to its model-based design. Updating the model updates the tests. - **Eggplant**: Maintenance can be higher, especially with frequently changing UIs, as tests rely on image recognition. 5. **Integration & Ecosystem**: - **Tosca**: Integrates well with DevOps tools, offering a suite for end-to-end testing. - **Eggplant**: Also integrates well, with a focus on user experience testing and monitoring. **Conclusion**: - **Tosca** is best for large enterprises needing robust, scriptless automation. - **Eggplant** is ideal for those needing flexible, cross-platform testing with a focus on UI. Choose based on your specific needs, platform requirements, and maintenance preferences. ---

outa? anyone else using this tool for oracle testing?

script now with Tosca or wait until it's installed on its permanent server... pros and cons... ### Waiting Until Tosca is Installed Where it Will Eventually Reside **Pros:** 1. **Consistency in Environment:** - Ensures that the scripts are developed in the actual environment where they will run, reducing the risk of environment-specific issues. 2. **Accurate Performance Metrics:** - Allows for accurate measurement and tuning of performance in the target environment, ensuring that the scripts perform optimally. 3. **Stability:** - Reduces potential disruptions and complexities associated with migrating scripts and settings from one server to another. 4. **Configuration Management:** - Ensures that all configurations, settings, and integrations are tailored to the final environment from the start. **Cons:** 1. **Delayed Start:** - If there are delays in setting up the final environment, it can delay the start of the scripting process and overall project timeline. 2. **Initial Setup and Testing:** - May require more upfront work to ensure the final environment is perfectly set up, which can be time-consuming. ### Starting to Script on a Temporary Server and Migrating Later **Pros:** 1. **Immediate Progress:** - Allows the scripting team to start work immediately, potentially speeding up the overall project timeline. 2. **Flexibility:** - Provides flexibility in resource allocation and can be useful if the final environment is not ready yet. 3. **Early Problem Identification:** - Early scripting and testing can help identify potential issues sooner, even if they are environment-specific. **Cons:** 1. **Migration Challenges:** - Scripts may need adjustments during migration to the final environment, which can introduce bugs and require additional testing and validation. 2. **Duplicate Efforts:** - Might require rework to align scripts with the final environment’s specific configurations and settings. 3. **Inconsistent Performance Metrics:** - Performance testing and optimization done on a temporary server may not accurately reflect the performance in the final environment. 4. **Integration Issues:** - Temporary setups may not fully replicate the integrations and dependencies of the final environment, leading to integration issues during migration. In summary, the decision depends on balancing the need for immediate progress with the potential complexities and risks of migration. If the final environment will be available soon, it might be worth waiting. If there are significant delays expected, starting on a temporary server with careful planning for migration could be beneficial.