We are #hiring Job Title #Senior #Automated #UI #Testing #Engineer (#Selenium) Location #Parsippany #NewJersey #usajobs #onsite #project #management #agile #testing #efficiency #artmac #artmacllc #artmacjobs https://lnkd.in/gppQdVsm
Artmac’s Post
More Relevant Posts
-
A fun fact about our hiring process is that we always provide a detailed #codereview to people who solve the assignment, and a code walkthrough during technical interview. Besides the solution functionality, candidates get feedback on code cleanliness, modularity, adherence to coding principles, tests, and so on. 💡 This, and many other people-related topics, have been covered in our recently published #EmployeeHandbook. Our Employee Experience Associate, Irma, dug further into our motivation to publish it. Find the link to the Handbook in the comments below, as well as a 24sata article covering the topic. 👇 #leapwise #buildingpeopleandsoftware #solidprinciples
To view or add a comment, sign in
-
⚡Manual/Automation (QA) 🔎 ⚡18.1k+ LinkedIn Family 🚀 ⚡Core Java ⌛ ⚡Selenium 🌐 ⚡10+ Websites Testing 🖥️ ⚡50+ Apps Testing (IOS/Android) 📲 ⚡UI/UX Testing 🌈 ⚡Postman 🌀 ⚡Database Testing 📥
✓ Most Asked Manual Testing Interview Questions.....!! 📝 Severity vs. Priority: Understand the key difference between Severity (impact of a defect on the system) and Priority (importance of fixing a defect). 📝 Bug Life Cycle: Learn about the stages a bug goes through, from identification to closure, in the Bug Life Cycle. 📝 Logging Bugs: How to log bugs effectively in the system? Share your approach and best practices. 📝 GUI Testing vs. Functional Testing: Explore the distinctions between GUI Testing (User Interface testing) and Functional Testing (testing features and functionality). 📝 Integration Testing: Dive into Integration Testing and its significance in ensuring smooth interactions between different components/modules. 📝 Dry Run in Cucumber: Explain the concept of "Dry Run" in Cucumber testing and how it aids in identifying errors. 📝 Sanity Testing: Define Sanity Testing and its purpose in ensuring that a software build is stable enough for detailed testing. 📝 Retesting and Regression Testing: Differentiate between Retesting (testing fixed defects) and Regression Testing (ensuring new changes don't impact existing functionality). 📝 SDLC - Software Development Life Cycle: What is SDLC? Provide an overview of the different phases involved in software development. 📝 STLC - Software Testing Life Cycle: Elaborate on the STLC and its stages, from Test Planning to Test Closure. 📍 Attributes of a Test Case: Discuss the essential attributes that a well-designed test case should possess. 📍 Low/High Priority and Severity Defects: Provide examples of Low and High Priority with Low and High Severity defects. 📍 Equivalence Class Partitioning: Explain the Equivalence Class Partitioning technique for test case design. 📍 End-To-End Testing: Explore the significance of End-To-End Testing, ensuring the entire application flows seamlessly. 📍 Smoke vs. Sanity Testing: Understand the differences between Smoke Testing (quick validation of major functionalities) and Sanity Testing (basic validation after fixes). 💡 Boost your Manual Testing knowledge and prepare for your next interview.....!! 💡 #manualtesting #softwaretesting #interviewprep #qualityassurance #testinglifecycle #buglifecycle #testcases #interviewtips #techinterview #testingskills #qualityengineering #sdlc #stlc #qaengineer #testingtechniques
To view or add a comment, sign in
-
Technical Consultant in TCS BENGALURU|| 🟩Certified ScrumMaster® ||🟩35K LinkedIn Family.|| Web Accessibility Test Lead ||Automation Tester|| PMO Operations||🟩7 Million Content Views.
📌 𝑻𝒆𝒄𝒉 𝑴𝒂𝒉𝒊𝒏𝒅𝒓𝒂 | 𝑻𝒆𝒄𝒉𝒏𝒊𝒄𝒂𝒍 𝑾𝒓𝒊𝒕𝒆𝒓| 𝑩𝑨𝑵𝑮𝑨𝑳𝑶𝑹𝑬| 𝑶𝑷𝑬𝑵𝑰𝑵𝑮 Check Job details from the link given and application link is given there- https://lnkd.in/dNBm5zrp Job Summary To create and maintain the documentation as per client requirement and agreed specification. Participate in documentation planning processes. Understand the product/feature. Check for GUI (Graphic User Interface) changes. Understand the impact of the new feature. Collate, edit and modify content in various kinds of documents by being actively involved in the product delivery lifecycle. Test the product/feature based on the documented procedure. Participate and interact as a collaborative member in all project team meetings and suggest enhancements for meeting quality standards. Learn the tools needed to develop documents for the particular project. Support the documentation development life cycle (DDLC) and contribute to the development of internal documentation standards and methodology.
Technical Writer
careers.techmahindra.com
To view or add a comment, sign in
-
Immediate joiner||Software Engineer @TechMahindra |⭐ 7K+Follower | Automation Engineer | Java | Selenium | BDD Cucumber | Regression | Robot Framework | ServiceNow | Jira | Agile Methodology | Azure Devops |
✓ Most Asked Manual Testing Interview Questions.....!! 📝 Severity vs. Priority: Understand the key difference between Severity (impact of a defect on the system) and Priority (importance of fixing a defect). 📝 Bug Life Cycle: Learn about the stages a bug goes through, from identification to closure, in the Bug Life Cycle. 📝 Logging Bugs: How to log bugs effectively in the system? Share your approach and best practices. 📝 GUI Testing vs. Functional Testing: Explore the distinctions between GUI Testing (User Interface testing) and Functional Testing (testing features and functionality). 📝 Integration Testing: Dive into Integration Testing and its significance in ensuring smooth interactions between different components/modules. 📝 Dry Run in Cucumber: Explain the concept of "Dry Run" in Cucumber testing and how it aids in identifying errors. 📝 Sanity Testing: Define Sanity Testing and its purpose in ensuring that a software build is stable enough for detailed testing. 📝 Retesting and Regression Testing: Differentiate between Retesting (testing fixed defects) and Regression Testing (ensuring new changes don't impact existing functionality). 📝 SDLC - Software Development Life Cycle: What is SDLC? Provide an overview of the different phases involved in software development. 📝 STLC - Software Testing Life Cycle: Elaborate on the STLC and its stages, from Test Planning to Test Closure. 📍 Attributes of a Test Case: Discuss the essential attributes that a well-designed test case should possess. 📍 Low/High Priority and Severity Defects: Provide examples of Low and High Priority with Low and High Severity defects. 📍 Equivalence Class Partitioning: Explain the Equivalence Class Partitioning technique for test case design. 📍 End-To-End Testing: Explore the significance of End-To-End Testing, ensuring the entire application flows seamlessly. 📍 Smoke vs. Sanity Testing: Understand the differences between Smoke Testing (quick validation of major functionalities) and Sanity Testing (basic validation after fixes). 💡 Boost your Manual Testing knowledge and prepare for your next interview.....!! 💡 Do like , comment & repost , if you find it helpful. Follow Payal Kumari for more insightful updates and tips related to Testing. #ManualTesting #SoftwareTesting #InterviewPrep #QualityAssurance #TestingLifeCycle #BugLifeCycle #TestCases #InterviewTips #TechInterview #TestingSkills #QualityEngineering #SDLC #STLC #QAEngineer #TestingTechniques
To view or add a comment, sign in
-
Kirtana Consulting's commitment towards meeting the expectations and requirements is based on two key principles of the state of the art technology and commitment to quality. #kirtanaconsulting #kirtanaconsultinguk #ukitservices #itservices #softwaredevelopment #itstaffing #webdevelopment #testing #consultingservices #softwaredevelopment #ukjobs #hiring #kirtana #clients #itstaffing #staffing #commitment #expectations #quality #requirements #key #principles
To view or add a comment, sign in
-
-
⚡Manual/Automation (QA) 🔎 ⚡18.1k+ LinkedIn Family 🚀 ⚡Core Java ⌛ ⚡Selenium 🌐 ⚡10+ Websites Testing 🖥️ ⚡50+ Apps Testing (IOS/Android) 📲 ⚡UI/UX Testing 🌈 ⚡Postman 🌀 ⚡Database Testing 📥
✓ Most Asked Manual Testing Interview Questions.....!! 📝 Severity vs. Priority: Understand the key difference between Severity (impact of a defect on the system) and Priority (importance of fixing a defect). 📝 Bug Life Cycle: Learn about the stages a bug goes through, from identification to closure, in the Bug Life Cycle. 📝 Logging Bugs: How to log bugs effectively in the system? Share your approach and best practices. 📝 GUI Testing vs. Functional Testing: Explore the distinctions between GUI Testing (User Interface testing) and Functional Testing (testing features and functionality). 📝 Integration Testing: Dive into Integration Testing and its significance in ensuring smooth interactions between different components/modules. 📝 Dry Run in Cucumber: Explain the concept of "Dry Run" in Cucumber testing and how it aids in identifying errors. 📝 Sanity Testing: Define Sanity Testing and its purpose in ensuring that a software build is stable enough for detailed testing. 📝 Retesting and Regression Testing: Differentiate between Retesting (testing fixed defects) and Regression Testing (ensuring new changes don't impact existing functionality). 📝 SDLC - Software Development Life Cycle: What is SDLC? Provide an overview of the different phases involved in software development. 📝 STLC - Software Testing Life Cycle: Elaborate on the STLC and its stages, from Test Planning to Test Closure. 📍 Attributes of a Test Case: Discuss the essential attributes that a well-designed test case should possess. 📍 Low/High Priority and Severity Defects: Provide examples of Low and High Priority with Low and High Severity defects. 📍 Equivalence Class Partitioning: Explain the Equivalence Class Partitioning technique for test case design. 📍 End-To-End Testing: Explore the significance of End-To-End Testing, ensuring the entire application flows seamlessly. 📍 Smoke vs. Sanity Testing: Understand the differences between Smoke Testing (quick validation of major functionalities) and Sanity Testing (basic validation after fixes). 💡 Boost your Manual Testing knowledge and prepare for your next interview.....!! 💡 Do like , comment & repost , if you find it helpful. Follow Rushikesh Patil for more insightful updates and tips related to Testing. #ManualTesting #SoftwareTesting #InterviewPrep #QualityAssurance #TestingLifeCycle #BugLifeCycle #TestCases #InterviewTips #TechInterview #TestingSkills #QualityEngineering #SDLC #STLC #QAEngineer #TestingTechniques
To view or add a comment, sign in
-
Interviewers ask, do I invent? Work independently? Found processes? Build CI/CD/test systems/service layers/data stores from the ground up? Install, configure, document. and maintain? Lead the way? Well, yah. The good news is that I'm self-guiding. Set a goal and I will figure out how to achieve it consistent with our priorities and commitments. The bad news is that I'm self-guiding. You asked for an independent thinker, remember. A wise request. You got one. That's the thing that make me effective. If you let it. You get a beautiful fit, I promise. - Lew Bloch, software that fits
To view or add a comment, sign in
-
-
🚨 Software testing interview questions (part 3). Q7. Define usability testing. A7.The process of defining an application to ensure that it is easy to use and user-friendly is known as usability testing. The features involved in this testing are navigation, user interface, and user experience. Q8. List the advantages of automated testing. A8. -Testing is faster in automated testing. -It is more reliable. -It is more efficient than manual testing. -Automated testing is more efficient than manual testing. -It can perform repetitive tasks. The tasks and tests performed by automated testing are sometimes impossible for humans to perform or understand. Q9. Define API. A9. API or Application Programming Interface is a means of communication between two software. It abstracts a program’s internal workings and complexities and allows the user to focus on the inputs and outputs required to use it. ❤️ لا تنسونا من دعواتكم ❤️ 🚨 Follow for more ❤️ 🚨 leave a comment for support or ask. #istqb #softwaretesting #manualtesting #QA #QC #Interview
To view or add a comment, sign in
-
-
Software Engineer || React JS ¦ React Native ¦ Next JS || C++ ¦ Python ¦ JavaScript || Full Stack Web & App Dev
Important to understand for better coding.
SDE at Microsoft | Founder of InterviewCafe | Former Co-Founder of AlgoTutor | Author | Public Speaker | Judge | Featured on Humans of Bombay (2x) & JoshTalks (3x) | Top News Features | All India Topper | Content Creator
🔄 𝐂𝐈/𝐂𝐃 𝐂𝐨𝐦𝐩𝐨𝐧𝐞𝐧𝐭𝐬 𝐄𝐱𝐩𝐥𝐚𝐢𝐧𝐞𝐝 𝐢𝐧 𝐒𝐡𝐨𝐫𝐭! CI/CD (Continuous Integration and Continuous Deployment) is a set of practices that automates the software development and delivery process. It helps teams to build, test, and deploy code more quickly and reliably. Here is a simplified explanation of the core components of CI/CD: 𝐂𝐨𝐝𝐞 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭: This is where developers write the code for the software. 𝐒𝐭𝐚𝐭𝐢𝐜 𝐂𝐨𝐝𝐞 𝐀𝐧𝐚𝐥𝐲𝐬𝐢𝐬: This is where the code is analyzed for potential errors and quality issues. 𝐆𝐢𝐭 𝐑𝐞𝐩𝐨𝐬𝐢𝐭𝐨𝐫𝐲 (𝐒𝐂𝐌): This is a system where the code is stored and managed. It allows developers to track changes to the code and collaborate with each other. 𝐂𝐨𝐧𝐭𝐢𝐧𝐮𝐨𝐮𝐬 𝐈𝐧𝐭𝐞𝐠𝐫𝐚𝐭𝐢𝐨𝐧: This is where the code is automatically built and tested every time a change is made. This helps to ensure that the code is always in a working state. 𝐉𝐞𝐧𝐤𝐢𝐧𝐬: This is a popular tool that is used to automate and manage CI/CD pipelines. 𝐓𝐞𝐬𝐭𝐢𝐧𝐠: This is where the software is tested to ensure that it meets the requirements and is free of bugs. 𝐀𝐫𝐭𝐢𝐟𝐚𝐜𝐭𝐨𝐫𝐲: This is a repository where the build artifacts are stored. Build artifacts are the files that are produced by the build process, such as compiled code and test results. 𝐒𝐭𝐨𝐫𝐚𝐠𝐞 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭: This is the process of managing the storage of the build artifacts and other related assets. 𝐁𝐮𝐢𝐥𝐝 𝐓𝐫𝐢𝐠𝐠𝐞𝐫𝐬: These are the events that initiate the CI/CD process, such as a code change being pushed to the Git repository. 𝐃𝐞𝐩𝐥𝐨𝐲𝐦𝐞𝐧𝐭 𝐒𝐭𝐫𝐚𝐭𝐞𝐠𝐲: This is the plan for how the software will be deployed to the production environment. 𝐃𝐞𝐛 𝐈𝐦𝐚𝐠𝐞: This is the deployment package that is created by the CI/CD pipeline. 𝐒𝐭𝐚𝐠𝐢𝐧𝐠/𝐓𝐞𝐬𝐭: This is an environment where the software is deployed and tested before it is released to production. These are just the basic components of CI/CD. There are many other tools and practices that can be used to create a more complex and sophisticated CI/CD pipeline. Follow 👉 Santosh Kumar Mishra for more📚 #systemdesign #cicdpipelines #interview
To view or add a comment, sign in
-
-
Project Management - Engineering | Banking Domain | PMP Practice | Agile Program Management | Scrum Master | Solution Provider | Facilitator
concept of continues integration and deployment
SDE at Microsoft | Founder of InterviewCafe | Former Co-Founder of AlgoTutor | Author | Public Speaker | Judge | Featured on Humans of Bombay (2x) & JoshTalks (3x) | Top News Features | All India Topper | Content Creator
🔄 𝐂𝐈/𝐂𝐃 𝐂𝐨𝐦𝐩𝐨𝐧𝐞𝐧𝐭𝐬 𝐄𝐱𝐩𝐥𝐚𝐢𝐧𝐞𝐝 𝐢𝐧 𝐒𝐡𝐨𝐫𝐭! CI/CD (Continuous Integration and Continuous Deployment) is a set of practices that automates the software development and delivery process. It helps teams to build, test, and deploy code more quickly and reliably. Here is a simplified explanation of the core components of CI/CD: 𝐂𝐨𝐝𝐞 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭: This is where developers write the code for the software. 𝐒𝐭𝐚𝐭𝐢𝐜 𝐂𝐨𝐝𝐞 𝐀𝐧𝐚𝐥𝐲𝐬𝐢𝐬: This is where the code is analyzed for potential errors and quality issues. 𝐆𝐢𝐭 𝐑𝐞𝐩𝐨𝐬𝐢𝐭𝐨𝐫𝐲 (𝐒𝐂𝐌): This is a system where the code is stored and managed. It allows developers to track changes to the code and collaborate with each other. 𝐂𝐨𝐧𝐭𝐢𝐧𝐮𝐨𝐮𝐬 𝐈𝐧𝐭𝐞𝐠𝐫𝐚𝐭𝐢𝐨𝐧: This is where the code is automatically built and tested every time a change is made. This helps to ensure that the code is always in a working state. 𝐉𝐞𝐧𝐤𝐢𝐧𝐬: This is a popular tool that is used to automate and manage CI/CD pipelines. 𝐓𝐞𝐬𝐭𝐢𝐧𝐠: This is where the software is tested to ensure that it meets the requirements and is free of bugs. 𝐀𝐫𝐭𝐢𝐟𝐚𝐜𝐭𝐨𝐫𝐲: This is a repository where the build artifacts are stored. Build artifacts are the files that are produced by the build process, such as compiled code and test results. 𝐒𝐭𝐨𝐫𝐚𝐠𝐞 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭: This is the process of managing the storage of the build artifacts and other related assets. 𝐁𝐮𝐢𝐥𝐝 𝐓𝐫𝐢𝐠𝐠𝐞𝐫𝐬: These are the events that initiate the CI/CD process, such as a code change being pushed to the Git repository. 𝐃𝐞𝐩𝐥𝐨𝐲𝐦𝐞𝐧𝐭 𝐒𝐭𝐫𝐚𝐭𝐞𝐠𝐲: This is the plan for how the software will be deployed to the production environment. 𝐃𝐞𝐛 𝐈𝐦𝐚𝐠𝐞: This is the deployment package that is created by the CI/CD pipeline. 𝐒𝐭𝐚𝐠𝐢𝐧𝐠/𝐓𝐞𝐬𝐭: This is an environment where the software is deployed and tested before it is released to production. These are just the basic components of CI/CD. There are many other tools and practices that can be used to create a more complex and sophisticated CI/CD pipeline. Follow 👉 Santosh Kumar Mishra for more📚 #systemdesign #cicdpipelines #interview
To view or add a comment, sign in
-