Tag Archives: Software testing

Google Puppeteer

Puppeteer : Is it time to ditch Selenium?

Automation Testing Tools, JavaScript, Software QA Testing, ,

Google has introduced a new library based on Chromium’s dev tool protocol. The library grants high-level API to interact with chromium and handle most tasks which you can perform using Chromium dev tools. The library is implemented in node.js and is really easy to get started once you install required packages using the node package manager.

……………………………………………………………………………………………………

Why Puppeteer?

Puppeteer flexes its muscle where selenium misses out. It is not just limited to interactions with the web application under test performing tasks like for e.g. interacting with dom, submitting forms, generating screenshots and pdf of web pages but also in intercepting network activity, throttling CPU and network, generating timeline trace and mocking API amongst some. The puppeteer can be easily be used to write end-to-end automation test suites with the benefit of getting a detailed timeline of the performance of all the assets (images, javascript files and so on).

Engineers can easily switch between headless and non-headless modes. While writing the automation suite, non-headless mode gives a good view of how the browser is interacting with the application under test and helps in debugging; just like in Selenium. But in production, we can execute suite in a headless mode as it reduces execution time and save resources.

……………………………………………………………………………………………………

Is it really that Good?

Yes, it enjoys the goodness of async code execution. You can always perform multiple tasks simultaneously following the latest javascript async await conventions. You can test the behavior of your application under different screen sizes. The network can be throttled on demand to find out how your application will run at low internet speeds. For e.g. if you want to test the error messages in an application when a user loses internet connectivity, puppeteer can easily handle such a scenario. Mocking APIs can also be achieved with utmost ease. For instance, if you want to test your “payment completed” screen but don’t want to go through the payment gateway flow, you can easily perform it with puppeteer by mocking the API response. With a detailed performance matrix, puppeteer can easily be used for performance testing.

So what are the drawbacks?

Google puppeteer supports only Chromium and Chrome out of the box. Third party implementations are available for Firefox and Internet Explorer. But they are experimental as of now and are missing a good chunk of the firepower. The documentation available is minimal as compared to selenium.

Why should you prefer Puppeteer over Selenium?

The targeted audience is the major deciding factor. If it majorly comprises of Chrome users you should go ahead with Puppeteer. Other factors include performing automation tasks which are not possible with selenium, like testing Chrome extensions, mocking API calls and so on. Selenium follows WebDriver protocol and has been from a very long time in the market compared to puppeteer hence itis better documented compared to puppeteer.

……………………………………………………………………………………………………

Conclusion

Puppeteer is a powerful library which has revolutionized the automation testing by overcoming functionalities missing in WebDriver protocol used by Selenium. Although it is still in the early stages, it promises a bright future, backed up as it is by the illustrious Chrome dev tools team.

……………………………………………………………………………………………………

If you have any queries in this field, talk to Mindfire Solutions. For over 19+ years now, we have been the preferred Software Development Partner of over 1000+ Small and Medium-sized enterprises across the globe.

Spread the love
  • 1
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
    1
    Share

Why should you outsource Software QA Testing?

Software QA Testing, , Mindfire Solutions
Outsource Software QA Testing
Outsource Software QA Testing

Nowadays, consumers access the same software application on varying devices, platforms, and browsers. Your software application must functional flawlessly and deliver richer user experience across different user environments to become profitable. You need to perform elaborate software QA testing to assess the quality and user experience of the software properly. To assess the quality of the software properly, you need to perform various types of software testing – functional testing, performance testing, usability testing, integration testing, acceptance testing, and beta testing. Also, you have to repeat the tests across various devices, platforms, browsers, and networks to generate more reliable test results. Continue reading Why should you outsource Software QA Testing? →

Spread the love
  • 7
  • 2
  •  
  • 2
  •  
  •  
  •  
  •  
  •  
    11
    Shares

Why Automation – Is it worth?

Software Engineering, Software Quality, , , ,

Automation Testing

Automated testing is need of the hour. Possibilities of the automation, apart from custom manual testing, are being analyzed for every other application now-a-days. It is preferred to manual testing due to several factors such as improved accuracy of tests, wider test coverage, more reliable results and above all, it saves time and cost rapidly.

Testing manually, on the other hand, is time consuming and error prone, hence can result in defects being left out. Having said that, I would like to analyze the positives of automated testing over manual as is generally said. Basically, it’s not always advisable to automate the AUT (Application under test) as opposed to prevalent myth about automation.

Automation can be accurate in giving reliable results with wider test coverage while saving time and cost, but this may not always be the case with all AUTs. Imagine the AUT with ever-evolving requirements and dynamic webpages. Here, Automation may be accurate with wider test coverage but will consume much more time and cost giving unreliable results due to system instability. In case of UI based AUT, if design changes frequently the automation is strictly discouraged. Further, choosing an inappropriate tool can lead to reduced efficiency as tool selection largely depends upon the technology used in the AUT.

It can be said that automation is the best way to increase the effectiveness, efficiency and test coverage of testing but only when proper analysis of AUT is made before shifting to it, else certainly a bad idea if its objective is not clear. Also, deciding on what to automate is most vital task before planning any automation process to follow. It is not possible to automate everything ; nevertheless modules that are stable and are manually tested at least once should be taken for automation. Test Cases that are executed repeatedly and consume time could be a priority, making the automation best suited for regression testing or retesting of the fixed issues. Descriptive test cases that are clearly explained are automatable and not the vague ones. Apart from regression, it can test stress, load and performance of the AUT.

Hence, Automation should be taken up only after analyzing the AUT and determining if the automation will actually be time and cost effective or otherwise.

Spread the love
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  

A Glass of Google, Anybody?

Software Industry, Thoughts, , , ,

Alternatively called revolutionary and creepy, Google Glass has cyberspace up – up in arms and up for it. Hate it or like it, you can’t ignore it.

There are social, privacy and etiquette implications. Not surprisingly, places where privacy is paramount (such as dive bars), have banned Google Glass. This makes headlines because…nobody knows!

And then there are positive applications such as surgeons monitoring indicators without having to look away. This makes headlines because…nobody knows!

Nobody knows what will happen to Google Glass.

You can’t even put it in any one slot. Is it technology? Is it fashion? Is it vanity? Is it utility? Is it the first attempt at mass wearables? Is it the advent of the cyborgs? It doesn’t end.

The best way to think about Glass is by closing your eyes.

If the downsides are mostly about inappropriate use or privacy concerns, the assumption is that wearers will never take them off. Given that it is easy to take off, it is is easy to see that people will just adapt and remove them at inappropriate places.

The question is: what utility can it provide?

Consumer uses are highlighted by Google. However, I feel specific work applications will come up as developers and organizations re-imagine the possibilities. You can use live-streaming for experience-sharing among friends, or field support personnel can use live-streaming to transmit a malfunctioning machine’s innards to an expert. You are an augmented human being with capability to see additional relevant information to the task at hand.

How can custom software development be impacted? One idea: a constantly recording Glass app with N-recent-minutes recording will mean that testers always have access to what they just saw – elusive bugs which cannot be reproduced will always be captured.

Every industry will have ideas of its own on what Glass can do for them. If Glass can make nurses more accurate, real-estate agents more responsive, students more attentive – you will use them.

Will you look uber cool or downright stupid wearing them? Will you care, if it helps you do things better and faster?

Spread the love
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
Testing at Mindfire

When in Testing do as the Testers do!!!

Software Quality, , , , ,

Its high time to bridge a gap between theoretical knowledge and real world implementation.
If you are new to testing domain and just trying googling out the real meaning and approach of testing below are few points which I feel will be handy for a beginner.

– Prepare test cases or a checklist for the project you are assigned in. Include all the test scenarios you can think of. Yes you are thinking right!

 

P.S. All the positive and negative scenarios. 🙂

For beginners – Test a simple ’email log in’ page!
What all scenarios you guys can think of!Yes you are going on right track.. whatever weired comes to your mind..Just do not stop playing around.

P.S. Let the application crash!!! 🙂

– Start performing tests , find and report bugs but hang on always remember there’s no end to bugs i.e. you can never say ‘This application is bug free’!!

P.S. Cant help it! 🙁

– Step into Customer’s shoes ; feel like a lay man and you will be amazed to see the number of bugs you come across.

P.S. Do not end up stepping on toes! 🙁

– Be Creative in your approach ; while writing test cases or preparing a check list. Do not assume.

P.S. Assumptions is the mother of all mistakes! 😉

– Start Suggesting ; Dig into the details and get to know the product’s functionality and general behaviour. This will enable you to add value and suggest new features and enhancements to your product.

P.S. A smart move it is! 😉

Last but not the least..

– Follow Processes ; Stick to the organisation standards and guidelines and process of QA testing.

P.S. Follow the process and find as many bugs you can..after all we are a part of software QA testing team !! 🙂

Happy Testing!!! 😀

Author – Anisha Nayak

Spread the love
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
Why Do You Do Things You Do?

Few things to consider before testing any application

Software Quality, Thoughts, , , , ,

I have a wall-pWhy Do You Do Things You Do?aper on my desktop which says: – “Why Do You Do The Things You Do” which forced me to write something like this which i feel should be considered before testing any application: –

1. Learning: – Analyze your test results thoroughly. Do not confuse yourself with ‘pass’ or ‘fail’ but finding the root reason of ‘fail’ or ‘pass’ will give you an idea for the solution of the problem. Testers knowledge increases by sending solutions for the problem

2. 100% of anything is not possible so having 100% test coverage is not possible but we can try to touch 99% of perfection.

Continue reading Few things to consider before testing any application →

Spread the love
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  

18 things to keep in mind while testing any application

Quality Assurance, Thoughts, , Sudeep Pattnaik

In the world of software QA testing, mastering the best practices is the key to success. This article presents 18 essential tips for QA professionals. From thorough test result analysis to maximum coverage and negative scenario testing, it covers a range of critical aspects. It emphasizes the importance of dividing applications into modules, early test case preparation, and involving testers from the start. The significance of regression testing, performance testing, and thinking beyond requirements is highlighted. Effective communication, prioritization, and continual learning round out the best practices, ensuring QA testers excel in their field and deliver high-quality software products.

1) Thorough Analysis of the Test Results:
As a software QA testing professional, it is crucial to go beyond reporting bugs and provide a comprehensive analysis of the test results. Error logs can reveal valuable insights into the nature and root causes of defects. By including this analysis in the bug report, testers make it easier for developers to understand and address the underlying issues. This not only expedites the bug-fixing process but also fosters effective collaboration between testers and developers, leading to improved software quality. problem.

2) Attain Maximum Coverage:
While achieving 100% test coverage may be impractical, testers should strive to cover as many combinations and scenarios as possible. By employing a systematic and strategic approach, testers can maximize test coverage. This involves identifying key functionalities, critical paths, and representative data sets to ensure that the most critical aspects of the software are thoroughly tested. Additionally, testers can leverage techniques such as equivalence partitioning and boundary value analysis to optimize coverage and prioritize test cases.

3) Divide and Conquer:
To achieve maximum test coverage, it is beneficial to divide the application into smaller modules and write separate test cases for each module. This approach facilitates focused and detailed testing of individual components, ensuring comprehensive coverage across the entire system. By breaking down the testing effort into manageable units, testers can effectively address complexities, identify defects, and maintain a high level of quality throughout the software development lifecycle.

4) Emphasize Negative Scenarios:
In addition to testing positive scenarios, it is crucial to include test cases for negative scenarios or invalid conditions. This ensures that the software behaves correctly when exposed to unexpected inputs or error-prone situations. By deliberately testing edge cases, boundary conditions, and invalid inputs, testers can validate the system’s robustness, error-handling capabilities, and adherence to specifications. Thorough negative testing helps uncover vulnerabilities and ensures that the software remains stable, secure, and user-friendly in all scenarios.

5) The Right Mindset
Approach QA testing with the mindset of discovering defects and identifying areas for improvement. Instead of assuming the software is defect-free, maintain a critical perspective and actively seek out potential bugs. This mindset encourages a thorough examination of the software and motivates testers to conduct comprehensive tests, resulting in higher-quality products. A vigilant and inquisitive approach to testing helps uncover issues that may have otherwise gone unnoticed, promoting a culture of continuous improvement and defect prevention.

6) Early Test Cases preparation :
To optimize the testing process, it is beneficial to start test case preparation during the analysis and design phase. Involving testers early on enables a better understanding of the requirements and facilitates the creation of comprehensive test cases. By actively participating in requirements discussions, testers can gain insights into the system’s intended functionality, identify potential test scenarios, and ensure that test cases align with the expected outcomes. Early test case preparation contributes to improved test coverage and enhances the overall effectiveness of the testing effort.

7) Ready with Test Cases before the completion of development :
Rather than waiting for the completion of development, testers should aim to have test cases ready in advance. Providing developers with test cases during the development process allows them to analyze and validate their work against the expected outcomes. This proactive approach enables early defect detection, smoother collaboration between testers and developers, and reduces rework efforts. It also enhances the overall development process by ensuring that quality considerations are integrated from the outset.

8) Address “Regression” effectively:
Regression testing plays a critical role in ensuring that modifications or enhancements to the software do not introduce new defects or cause regressions in existing functionality. By including regression test steps within test cases, testers can perform quick regression checks during system testing itself. This approach saves time and effort by identifying and addressing regression issues early on, minimizing the risk of functional regression and maintaining the stability of the software.

9) Test the “Performance”:
For applications where response time is crucial, thorough performance testing is essential. Testers should design and execute performance tests to assess the application’s behavior under various load conditions, stress scenarios, and unfavorable environments. By simulating realistic workloads and analyzing performance metrics, such as response times, resource utilization, and scalability, testers can identify performance bottlenecks, optimize system performance, and ensure a seamless user experience.

10) Leave full spectrum Testing to QA:
To maintain objectivity and ensure a fresh perspective, it is generally advisable for testers not to test the code they have developed themselves. When individuals test their own code, there is a higher likelihood of overlooking mistakes or biases due to familiarity. Instead, encourage collaboration among developers and testers, enabling independent verification and validation of the software. This approach promotes rigorous testing and helps identify defects that may have been overlooked by the developer.

11) Think beyond Requirements:
While testing based on specified requirements is essential, testers should also explore scenarios that may not be explicitly mentioned in the documentation. By thinking creatively and applying domain knowledge, testers can identify potential risks, edge cases, and scenarios that may not have been considered during requirements gathering. This broader approach to testing helps uncover hidden defects, enhances software robustness, and contributes to a more comprehensive testing strategy.

12) Leverage Past Experiences and Data:
Learning from past experiences is invaluable in software QA testing. Testers can refer to historical data, statistics, graphs, and previous test results to identify defect-prone areas, determine common patterns, and allocate testing efforts accordingly. By leveraging this knowledge, testers can focus on critical areas, allocate resources effectively, and adapt their testing approach based on past trends and insights. This data-driven approach enhances the efficiency and effectiveness of the testing process.

13) Continuous Learning:
The field of software QA testing is continuously evolving, and testers should actively seek opportunities for learning and skill development. Throughout the testing process, testers encounter new terms, concepts, and technologies. Keeping a record of these learnings and documenting them in a personal knowledge base helps build a repository of valuable insights. These learnings can contribute to the preparation of test closure reports, facilitate knowledge sharing, and ensure continuous improvement in testing practices.

14) Early Involvement of the Testing team:
To achieve optimal results, it is advisable to involve testers from the early stages of the software development lifecycle. Engaging testers during requirements analysis and design phases allows them to gain a deep understanding of the application’s functional and non-functional aspects. This early involvement facilitates proactive test planning, identification of potential testing challenges, and the formulation of effective testing strategies. By participating in requirements discussions and design reviews, testers can contribute their expertise and ensure the development process is aligned with quality goals.

15) Share Best Practices:
To foster a culture of excellence and continuous improvement, testers should share their best practices with other QA testing professionals. By sharing insights, techniques, and lessons learned, testers can contribute to the growth and development of the testing community. This exchange of knowledge promotes collaboration, inspires innovation, and ensures that industry-wide best practices are shared and implemented consistently.

16) Effective Communication and Collaboration:
Testers should actively engage in discussions and maintain effective communication with developers, business analysts, and other stakeholders. Direct interaction helps clarify requirements, resolve conflicts, and ensure that everyone is on the same page regarding the expected behavior of the software. When conflicts or misunderstandings arise, timely face-to-face discussions or written communications (such as emails) should be used to address and resolve them. Effective communication fosters collaboration, reduces misunderstandings, and ensures a shared understanding of quality objectives.

17) Prioritization and Risk Management:
To optimize testing efforts, testers should prioritize their work based on risk analysis and project constraints. By identifying critical functionalities, high-risk areas, and potential showstoppers, testers can allocate their resources effectively. Prioritization ensures that testing efforts are focused on the most critical areas, reduces the risk of major defects slipping through, and facilitates risk-based decision-making throughout the project lifecycle..

18) Effective Bug Reporting:
Writing clear, concise, and detailed bug reports is crucial for effective communication between testers and developers. A well-crafted bug report includes not only the symptoms and steps to reproduce the bug but also provides the impact of the bug on the application. Testers should analyze the bug, include possible causes, and provide any additional information that aids in reproducing and fixing the issue. Well-documented bug reports expedite the debugging process, enable efficient collaboration between testers and developers, and ensure that issues are resolved accurately and promptly.

By implementing these practices, software QA testing professionals can enhance their effectiveness, improve the overall quality of the software, and contribute to the success of projects.

 

Spread the love
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  

I AM A BUG

Software Quality, , ,

BugHello folks ! Today I am going to tell you a story of three friends …. Yes you guessed it right, one of them is me . All three of us were a gang of notorious beings – blocking a code here, hiding a window there, disabling a button for the poor user or crashing the application a few times ! But we were living happily in our world until came in the big monster ‘The Tester’. Oh what a sweet fellow to begin with. He entered out territory with a gentle smile, its only later did we realize that he captured every corner of our house. He specially looked for the crevices and deep holes. God ! …. how difficult our survival became. Every morning when he came, we tried to hide ourselves and pray for the evening to come so that he would leave for the day. But how long could we, the tiny creatures survive this big bad monster and one day the inevitable happened and our lives changed forever.

Continue reading I AM A BUG →

Spread the love
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  

Attending Asia’s Biggest Software Testing Conference

Software Quality, , ,

Software Testing ConferenceThis was really a nice opportunity for me to attend a ‘International Software Testing Conference’. As a ‘Software Tester’ this is really great forum to meet to all great software testing experts and muster knowledge and expertise from them. This is really a huge canvas to expand our network for knowledge concerns. We came across this international event, & finally two of us were selected for the conference.

We zipped our baggage and flew to Bangalore on 11th May 2011 to attend the conference on 12th and 13th May 2011. On 12th May 2011 we had reached the conference spot with vibrant curiosity which was at ‘Hotel The Chancery Pavilion, Residency Road, Bangalore, INDIA’ for the quest of knowledge.

Attending The Software Testing Conference

We completed the registration process successfully and entered the conference hall. At 9 AM the conference just started with a welcome note. After the welcome note we were given with some highlights of the events for that day.

So this way the conference just started with a huge a surprise. On 12th first event was a KEYNOTE by Rob Lambert, Software Testing Club, UK. “Narrowing the Gap between Requirements and Testing: Feedback Loops, Agile and Communication”. Rob was explaining about the Agile process, and gap between requirements and testing. In normal testing life cycle we follow certain standards about writing testcase and executing the testcases in real time. Which takes a lot of time. But Rob explained that we don’t need
to bother about writing all the test cases where we can make a checklist and only need to check them while testing in agile process. Well some debates were there on this concept but at last we were able to understand to the importance of the process which was explained by Rob. I spoke to Rob about this concept and got some concepts cleared about agile software testing and methodology in real time testing.

The second event was “Define and Build Enterprise Automation Framework”, Speaker(s): JayaKrishnan Sashikumar & Preeth K P, Infosys. In this event they explained their own enterprise automation framework. Which was a requirement in of their projects. They were just explaining the architecture and model of the framework.

“Delivering Business Value through Test Automation” Speaker: Maruthi Sivakumar, AppLabs was the third event. Where MR Marithi Sivakumar was explaining about benefits of Test Automation and how test automation can help manual testers to do their job in better way so that the repetitive task can be done within less human interaction.

After three consecutive events we had a small energy break. And after the energy break the fourth eventjust started.

The fourth event was a KEYNOTE by Julian Harty, eBay, UK. “Pushing the boundaries of User Experience Test Automation”. Julian was explaining about the user experience test automation. Now a days usability is the most important factor for all kinds of application. So Julian was explaining about the ‘User Experience’, and ‘Usability’. How to automate Usability testing while observing the user experience. I had a long discussion with Julian about the ‘User Experience’, ‘Usability’, and ‘User Interface’. In the end I got my doubts clarified by Julian.
The fifth event was “Test Automation Rule Radial Hybrid Framework” Speaker: Velu S. P, IBM. Mr Velu has created his own Framework for test automation for his current project testing. After this there was a lunch break.

The sixth event was “Accelerating Regression Test Automation using Ready-to-use Test Automation Framework” Speaker(s): Chandrashekar S, Pallavi Jain & Vidyadhara C.A, Infosys. In this event the speaker has illustrated how test automation helps in regression testing. The seventh event was “Robust Automation Framework using Database for Test Data” Speaker(s): Sriharirao
Kuchi and Merral Crasto, IBM. In this event the speakers has shown how to use database for data driven testing. Instead of using a flat file or excel sheet for data driven testing they have just explained how database can be used for this purpose and how it is helps as compared to the other file formats which is very very dynamic in nature.

After this we had a small tea break. And after the break we had a Plenary Session by Pradeep Soundararajan, Moolya Software Testing, India “Achieving Personal Excellence as a Tester”. This session was really interesting where Pradeep was explaining what should be the true nature of a software tester. How a ‘Software Tester’ should be in ideal form. How to gain knowledge in Software Testing, and how to communicate with other testers and software testing experts all around the globe. Pradeep has suggested the ideal approach for testing and test management.

“Data Driven Automation Testing of Web Application using Selenium” Speaker(s): Navaraj Javvaji, Anand Sathiyaseelan, UmaMaheswari Selvan, AVA Corp was the eighth session. In this session the speakers were explaining about the selenium tool and how to use it for data driven testing.

So in this way 12th May is over and in the end I had a talk with experts for some real time problems in my early projects.

On 13th May 2011 we have reached the conference spot in the same way. After the registration the conference just started with a welcome note. After the welcome note we are given with some highlights for the events for that day.

The first session was about KEYNOTE by Sai Chintala, Applabs, India “Effective Performance Testing”. In this session Mr Sai from Applabs has explained about the basic concepts of Performance testing and how to do effective performance testing.

“Basics on Security Threats, Challenges and Countermeasures” Speaker: Narsimha Reddy, Infosys was the second session where Mr Narsimha from Infosys has explained core concepts of security threats for any application. Where in this session the discussion was for SQL injection, XSS attacks, Script inject and so on.

In the third session we had “Perform Fuzz on Application’s Web Interface”, Speaker: Aniket Kulkarni, Symantec. Mr Aniket Kulkarni works in Symantec as application security researcher. He was explaining about fuzzing techniques to test any application for security and load testing. How to fuzz any application and crash/break the application and check the logs for the crash. So in this way one can encounter about the security holes in the application. Also Aniket has explained how to capture packets transmitted
and analyze the packets for security threats. Overall this session was really nice and helpful.

“Benefits of Automated Security and Performance Testing of SAP HCM Applications” Speaker(s): Abhinav Gupta, Chandrashekar.S, Shahbaz Ali, Sharita Priya Castelino, Infosys was the fourth session. This session was all about SAP based application.

KEYNOTE by Mahesh Saptarshi, Symantec India, “Software Security – Technical Challenges”. This session was all about software security and negative testing. How can negative testing can lead to software security threat and business risk factors.

The sixth session was on “Performance Testing: A Catalyst for Swift IT” Speaker(s): Ashish Tyagi, Siddharth Joshi, Vivek Bal, Capgemini. Mr Siddharth explained about the performance testing and its implementation in web based application.

“Issues during Performance Testing and Solutions using various Tools and Tricks” Speaker: Amitabh Kaushal, IBM was the seventh session. In this session Mr Amitabh was explaining about the various tools and their usage. Some commercial and open source performance and load testing tools.

All sessions were really informative and useful. However I came across these things which I have learned and which will really add value to my current and future testing work:

• Agile methodology
• Automation testing and creating own automation framework
• User experience Test Automation
• Regression testing using automation testing
• Data driven testing using database, excel sheet, and flat file
• Data Driven Automation Testing of Web Application using Selenium
• Effective performance testing
• Application security threats, challenges, and countermeasures
• Fuzzing technique for web based interface
• Software security testing
• Various tools and tricks for performance testing of application

Likewise attending the sessions I got the prospect to meet, share, and interact with different technology experts from different other companies. We shared our views and work procedure on software testing and methodology we follow. This conference helped me in building my network in the world of Software testing,which will help me getting support and sharing opinions with these experts on different problems from time to time that we face in our day to day work life.

This conference was really a wonderful experience for me. I got to know so many new concepts, tools, techniques, and methodologies which is really going to help me in my work. In fact I have started working in the manner as we have learned from this conference. Well in this international conference I have got the exposure to real time industry experts and their views.

I feel lucky to be a part of Mindfire Solutions, not only for allowing me such a huge opportunity to explore knowledge. This is the beginning of opportunities and there is a long way to go with Mindfire on the path of success. This is really a grand experience for learning matter.

Mindfire is our company which always promotes, enables, and supports in all the initiatives for the career growth of all its employees. I feel good when I get these kind of opportunities. Well this makes me feel special in Mindire. I am also looking forward for the opportunities like this in the future to sharpen my skills and expertise in the Software QA Testing and Quality Assurance.

Spread the love
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •