Our Software Testing World Cup 2014 story – The Four Musketeers

Our team “The Four Musketeers” recently participated in the STWC 2014 testing competition in the North America region and were Rank 5/36 teams. To start with, I should say our team had a blast and it was so much fun right from the way the competition was advertised, presented and conducted.

My team experiences of the competition can be divided and explained in the following phases-

Preparation phase-

About 3-4 days before the competition, my team members went through the information provided in the website and noted down important details which would be valuable to get more points. Also, we researched various free tools available which may help us in testing in terms of doing functional and performance testing.

It is interesting to note that, my team was so into preparing for this competition that one of my team members  cut short his vacation in Canada just to join the competition in person and help our team out. Now, that is true dedication!!!

The next thing our team did was discussing testing strategies and approaches we could use for the competition.  We started looking into various  books and testing courses we have taken (mainly BBST and RST) and got some ideas from them.

Next thing was resources. What type of OS’s and devices we would need to test the product. After a lot of discussion, we ended up having 2 versions of Windows OS (XP and 7), Mac OSX and bunch of mobile devices and tablets, along with a multi – plug to connect a number of devices all at once for charging and power.

Finally we came to the collaboration piece. How is our team going to collaborate and discuss things during the competition? A team member came up with the idea of using Google docs for collaboration so that each one can see the other persons updates as and when he/she is doing stuff.

Brainstorming phase

Once we saw the e-mail hinting that we will be testing an image and video capture tool, my team started brainstorming various possibilities and combinations in terms of whether the application would be a desktop app, mobile app or a web app.  For each type of app, what should be our test strategy?

It is funny that, 3 hours before the competition we though about various image and video capture tools and my team mate said Snag it is a possibility. But, my team dismissed that idea thinking that the product may be something in the beta version not yet available to the end users (Unfortunately we were wrong :-( )

2 hours before the competition, we started looking at different tools like Jing, Camtasia and other tools and started comparing the features to get an idea about how these kinds of tools work.

Execution phase-

Based on the previous phases, my team had decided various resources and testing techniques that could be used during the competition.

At 5:30 PM EST,  we uploaded a doc which contained the important factors that would help in getting better scores and some rules of the competition on google docs and shared it with our team. We made sure everyone could access it.

At 6:00 PM EST,  I joined the You tube channel and saw Matt and the Snag it representative (Stakeholder). I increased the volume on my side so that my entire team could hear the conversations. I was in charge of monitoring the online session and typing in the questions which me and my team members wanted to ask. We also simultaneously started downloading the builds to our respective devices.

While doing this, the other 3 people started noting down important points the stakeholder was talking about and which he cares about.

At 6:30 PM EST, we started doing a Risk analysis.  We identified different areas which the stakeholder cared about  and started thinking about potential risks for each of those areas. Then we thought about impact and the likelihood of some problem occurring in that module and came up with Risk Scores.

At 6:50 PM – We had quickly completed the Risk Analysis and started assigning the test areas within each one of us and prioritized our testing based on the scores.

At 7:00 PM – We started testing based on the risk score. We continuously were discussing and comparing results. Our testing approach was Risk Based Exploratory testing. We decided to spend about 20 minutes in each of the test areas identified and then moved on to the next one.

At 9:00 PM – Me and another team member started working on the “Test Report” while the other 2 continued testing and posting defects.

At 9:30 PM – We submitted everything and were really happy about our effort.


As I said in the beginning my team had a blast. The competition was pretty intense as there were some confusions and tension for the entire 3 hours. But at last we pulled through it successfully.

Some interesting things were the different testing approaches our team came up with like using some tools to check application performance, trying to test on mobile device in different ways, trying to interface with external applications through the app and I tried connecting the laptop to multiple screens like my TV and tried playing recorded videos of snag it to check video quality and performance.  And of course the beer and the pizzas we had throughout the competition helped too :-)

One thing which our team did not expect was that, the name of the product we were testing was released at about 5:45 PM, although the testing was supposed to start only at 6:30 PM. My team was unaware that we could start testing once we got the e-mail with the product download link and also, we thought we need to ask some questions to the business customer and test based on the high risk areas (We still stick to this that it was worth testing based on risks instead of randomly testing modules). So, by the time we posted the 1st defect there were already 60 entries in HP Agile Manager. Probably it could be a good idea next time, if there is information about when a team can start testing.

Overall this testing competition was worth it and my team will be competing next year and will try to improve on the limitations we had this time.



Apple and Android software updates – The real story

I have personally talked to so many people about Apple and Android software updates. Believe me, there were lot of discussions, arguments, debates about this but some things I consistently heard was

  • “Apple updates are so seamless and the user gets it immediately”
  • “Android updates take forever to reach my phone. I want the latest build now but my phone does not support it”
  • “It has been 4 months now and still haven’t got the Android Kit Kat update”

Now why is this? why can’t Android follow the pattern of Apple and give the updates to all the loyal android users out there, as soon as the updates come up? I have talked to so many people about this and have told them the reasons from my point of view in terms of comparing two different eco-systems and expecting them to act the same way although they are different on multiple counts. The differences come in many forms-

  • Apple is just one manufacturer and all its phones and tablets use the same operating system whereas Android has different manufacturers different phones like HTC, Samsung, LG, Motorola and so on….. Each one of them have there own separate skin on top of the android OS.
  • Each apple device has the same type of hardware and thus all the software updates work seamlessly with the device. As for android, the manufacturers use different chipsets, different hardware, firmware and have to make sure the android updates are compatible with these. In most cases it is not and thus the wait, the delay and inability for all android users to get the updates instantly.
  • There are millions of android phones out there and expecting the same software upgrade patterns on all phones is impossible!!!! It is like all users expecting everyone to get the same interest rate, for say there savings account throughout the world just because they have bank accounts. The point is there are different banks, there are different regions, different rules and regulations etc. (Not the greatest of analogies but I think it hits the point :-) )

This article below nailed my thoughts exactly and gave more detailed description than I did to my colleagues. It perfectly captures the real reasons why the software updates work so differently in the Apple and Android devices.

Check it out here -> Link

Have any thoughts on this? Share it here :-)

Finally realized the difference between Adaptive and Responsive web design

For the past couple of months, while I was talking to different people about mobile testing, they kept using the term “Adaptive web design” and “Responsive web design” interchangeably. Initially, I thought they were the same but became more and more curious about the terms when a colleague of mine indicated that there are some differences.

I did some research and found that, they are technically NOT the same (my colleague was right :-)). I realized that people do not know the actual difference between the two and are using it interchangeably.

So, what is the actual difference between the two you may ask? Here it is-

Responsive web design - In this, you make the page responsive to the width of a browser window. So, as and when you keep resizing the browser you will see the page changing dynamically and giving the user the optimum page view in different “Browser” widths.

Most of the stuff is done on the client side thus leading to some performance constraints

Adaptive web design - In this, you give the user different versions of the page based on the device being used. There is a device detection script which runs on a web server and each time a user access the website using a device, the script detects the type of device the user is using and loads up the page accordingly. It DOES NOT have anything to do with the browser width and it is related to the device screen size.

Since most of the stuff is done on the server side, there is less problems due to page performance.

Although, the above 2 approaches have different types of implementations they are similar in terms of its goal  i.e giving the optimum experience to the user in terms of the page being displayed when accessed via a phone, tablet, phablet or a desktop browser.

I used the below links to get a better idea about the similarities and differences




So there you go. Finally I found the answer to my question and hopefully this gives some clarity to people who have the same doubts about the 2 designs in their mind.

Next time, you see a person using these terms interchangeably, what would you say? :-)





Why Mobile Web Testing and how to become good at it?

A couple of years ago, I got into a totally new domain of testing and have never repented my decision since then. Yes. I am talking about Mobile Web Testing. Before, getting into mobile web testing and my experience, let me give you a broader idea about the Mobile ecosystem, how it is changing the world and why we need to be part of this revolution.

On a high level the mobile ecosystem consists of Native, Web and Hybrid applications (apps).  Each one has its own advantages and disadvantages.  Understanding the difference between them is the first step towards becoming a good tester in the mobile space. I personally have worked with all 3 types of apps and understood that there are multiple factors in each one of them. A tester needs to be aware of this and think about test objectives, test approach, test design and test execution specific to the type of app being tested.

A majority of my testing experience is in the mobile web domain where I researched various approaches, tools and networked with so many mobile testers inside and outside my company to get a grasp of the subject. As a result, I came to a conclusion that I still have to learn so many things due to the ever changing nature of the mobile web domain and the mobile space as a whole.

Currently, the direction everyone is going towards is “Responsive Web design”. If you haven’t heard about this term, please stop reading any further and at least read the first paragraph of this link -> http://en.wikipedia.org/wiki/Responsive_web_design.  It is going to be almost mandatory for testers to know about this, as the world is heading in this direction and it is here to stay at least for the next couple of years or so. Examples of Responsive web sites are Microsoft, Disney, Boston Globe and there are others here at www.mediaqueri.es

Testing these responsive websites is a challenge as there are different devices, different form factors, different screen resolutions, different browsers and numerous other permutations. This being the case, I tried out different approaches that will help me become a better tester. Some of them are as follows-

  • Networking with inside/outside mobile testers and consultants.
  • Keeping updated with the latest in mobile technology.
  • Researching different tools to help out in testing
  • Trying to see how Rapid Software Testing approaches could help out in mobile testing.
  • Researching production defects. This is to help to focus testing on types of problems the users are seeing in the application.
  • Attending mobile focused conferences

So, from all the above description, you should have started to get an idea about the message I want to convey through this article. Still thinking!!! The answer is “Thinking out of the box”. Mobile being such a vast domain governed by multiple factors, it becomes all the more important to try out different approaches rather than just sticking to a set of scripted test cases and hoping you have the so called “100% Coverage”. These test cases are written usually by an individual who thinks he/she knows all the things affecting a particular module but the truth is “They Don’t” and for that matter no one does until a new feature is fully implemented, especially in the mobile web space.

I have seen this happen time and again throughout my experience as a mobile tester. So please do not fall into this trap of writing test cases for each and every thing. By doing this, you will end up consuming valuable testing time that could have actually been spent on exploring the application. The mantra I follow is “Very High level test cases complemented with Exploratory testing”.  Again, this worked for me on a real industry application which is used by millions of users in the US but is not a hard and fast rule. See which works best for your project but avoid pitfalls of completely relying on scripted test cases.

Finally, never hesitate to challenge anything when working in a mobile web project. “Always ask Questions”. The ugly truth is no one has any idea about how a new feature is going to implemented in responsive web design world (even if you have mockups). There are always challenges and the least you could do is, challenge ideas and question idealistic thinking which in turn would help to flush out ambiguities in requirements.

So join the mobile revolution and lets become good mobile testers!!!.

How to save battery life on mobile phones? – My thoughts

Recently, a colleague of mine asked me a question, “How to ensure the mobile apps do not consume too much battery life?” I thought this was an interesting question as I have always faced problems with battery, due to my insane usage patterns :-).

That being said, below were the steps I have taken which have helped me conserve battery life on my iPhone (This holds good for android phones too) and helps me give a feeling of control over the apps I have installed and my phone as a whole.

Here goes-

In general a mobile app will use too much battery life when-

 1. It uses location services like Facebook, FourSquare, .  What happens here is the app continuously keeps updating the current location of the user periodically, in certain time intervals and it drains lot of battery life.  Same holds good for actual GPS apps like Apple, google maps, mapquest etc.
You can disable this by going to Privacy -> Locations Services on your iPhone and there is something similar to this on android phones. This will force the application to get the user consent before figuring out the GPS coordinates.


2. If the app uses lot of images/animation and if it is constantly running in the background, the battery life drains.
For this, make sure you kill the application after you use it by double clicking on the “center button”  located at the bottom of your iphone and manually close that app.


3. Music related apps drains a lot of battery. Spotify, Pandora, iTunes. Same applies to Video players, Podcasts too.
Same as above


4. Screen brightness is one more thing which drains battery life.
The optimum way to fix this is go to Brightness & Wallpaper -> Select auto-Brightness for optimum battery life.


5. “Notifications” is one more thing to keep in mind. This is not a problem if you are using 5-6 apps. But, when you have 45 apps like me on your phone :-), then you have a problem.
you may want to control the Auto push notifications from different apps by going to Settings -> notifications.
Here you can individually control each apps notification mechanism.


6. “Browsing” is one more thing which obviously drains battery. From reading the news via BBC, Flipboard to reading books, articles etc all amounts to draining of battery life. This sometimes is unavoidable.


7. Recording Videos and playing the will of course affect battery life.


These are all the possible things I can think of right now which affects battery life, hope this helps in answering this question. If you have any other tips please feel free to share it here as it would be helpful to me and other readers.


Thanks all!!! Happy Testing!!!

HTML5 vs Native – The hot contenders for total web domination and the great mobile debate

Over the past 6 months,I have heard so many conversations  about HTML5 being slow, bad, has  no future and people should not consider it. Some may be true and some are totally false. Let’s analyze this further in the below sections-

We know Facebook and LinkedIn changed their applications from HTML5 to Native (I personally liked the LinkedIn HTML5 app). You can refer to their reasons of why they changed in the links below.



The reasons mentioned in the above links were very valid due to nature of the business Facebook and LinkedIn has with its customers. They were having problems with-

1) Performance issues – Running out of memory

2) Smoothness of animations

 3) Getting detailed information when things go wrong in production

All this was because both had millions of customers using and interacting with their app on a daily basis. The load/traffic was so heavy and performance was a major concern.

Just because these 2 companies dumped HTML5 and went native does not mean HTML 5 is dead because again

  • The nature of the business
  • The type of customers the app attracts
  • speed  to  market

are 3 VERY major things to consider before deciding on going the HTML5 or the Native way.

For example –

Let’s take a restaurant app. The sole aim of this app is just to show the different menu options they have. They don’t have any moving pictures or animations but have just static pictures of food. They also have their location displayed via Google maps API.  If a customer wants to order something, he clicks on the phone number link, which immediately loads the phone number on your phone and you can call them.

With this being the case, they could go the HTML5/Hybrid approach and get this app to the market quickly. They don’t need to create 2 native apps one for iPhone and Android as it could be costly to them. Also, the people who use the app may be a fraction of that of Facebook and LinkedIn. Probably only users who know about the restaurant bother to download the app and look into it.

Similarly, let’s take an insurance app. Do insurance apps have customers like Facebook and LinkedIn? NO. People who have GEICO, State Farm, and Progressive etc. interact with only the specific app based on their insurance type. In these cases, HTML5/Hybrid approach could work for them.

Like this there are many examples where probably going Native would be time consuming (for whatever reason), costly and not well suited to the type of business.

Firefox OS

We talked about apps, now coming to OS. People are bashing the new Firefox OS and so many people told me that it is waste of energy and time. But, do they know that, their initial sales of their phones went out of stock within a few hours (again you can argue with me that they may have put up only small number of phones compared to Samsung and Apple for sale, but still this is better than not any phone getting sold at all). Check this link out


At least based on the specs, the 2 phones Keon and Peak have relatively decent specs compared to other phones in the market currently. Also, since this is a developer version, it gives more flexibility to play with your phone and make it work as you want it.

In fact T-Mobile, Sprint and other carriers/partners have already decided to release phones with Firefox OS. Check out the list of partners here



So, to summarize, don’t write off anything as useless especially technology. If we do, then we are the most ignorant people on earth as we have seen time and again, how disruptive technology/companies like Dropbox, Samsung Galaxy line of phones, Instagram gave other people the run for their money (Literally!!!!).

I just wanted to write about this, to get these thoughts out of my mind. Let me know what you think about this or have any feedback.

Mobile, tablets, browser technology trends – 1st Quarter 2013 – Wrap up

There were so many people who talked to me about different technology trends happening in the mobile, tablets and browser space. Since, I generally keep track of these things, I thought I should highlight hot topics in technology happening each quarter in one blog post.

So, I decided to start with this blog post to give all the technology news which happened this quarter. I will try to give updates like this for the succeeding quarters in different blog posts.

Here goes…

Browsers- Firefox and Opera




  • http://www.engadget.com/2013/01/30/blackberry-10-event-roundup/#continued
  • This is going to decide the fate of Blackberry (In fact they change their name from RIM to Blackberry). They are really serious about this
  • Full touch phone
  • Buttons on the side of the phone
  • Has 2 ports – micro USB and micro HDMI connections
  • BB10 OS
  • Blackberry Hub feature, like the control panel of your computer
  • Releasing today with AT&T at $199 with contract. Will release in other operators in the next upcoming weeks.
  • http://bgr.com/2013/02/05/blackberry-10-android-apps-316402/
  • Blackberry planning to update their Android emulator to run Jelly Bean apps
  • You can port Android 4.0+ apps to BB10 platform.

Phone Specs (HTC One, Blackberry Z10, iPhone5, Nokia Lumia 920)

Apple iOS updates

  • iOS 6.1
    • adds Long Term Evolution (LTE) support to 36 additional iPhone carriers worldwide—or now 56 total.
    • ability to use Siri to purchase movie tickets in the U.S through Fandango
    • iTunes subscribers can download individual songs to their iOS devices from iCloud.


  • With just a few quick steps, it’s easy to open the phone app on any locked iPhone running iOS 6.1.
  • the process involves holding down the power button and aborting an emergency call.
  • iOS 6.1.1
    • This update fixes an issue that could impact cellular performance and reliability for iPhone 4S.
  • iOS 6.1.2
    • Fixes an Exchange calendar bug that could result in increased network activity and reduced battery life

iPhone5S and iPhone Mini rumours


  • Security Enhancements in Android 4.2.2
    • It includes a feature with which your users will be able to verify applications prior to installation thereby preventing harmful apps from entering the mobile device.
  • enables you to configure VPN in such a way that it will not have access to the network until a VPN connection is established
  • Ubuntu phone
    • Canonical – company
    •  The Touch Developer Preview can run on Nexus 7 and Nexus 10 tablets, as well as the Galaxy Nexus and Nexus 4 smartphones – Developer version

 Interesting Problems

  • new bug has been found on the Galaxy S III that can let users bypass the lockscreen and access all phone functions


  • Apple announced the 128GB iPad
  • its stainless steel frame and soft-touch back that’s available in gray or red. The device measures .42 inches thick (about the same as the Kindle Fire HD‘s .41 inches) and weighs 13.05 ounces, making this tablet lighter than the Fire (13.9 ounces) but heavier than the Nexus 7 (12 ounces).
  • Biggest advantage is – The Slate 7 has a microSD card slot and microUSB port.
  • 1024 x 600-pixel – resolution lower than kindle and nexus 7

Other Technology news

  • Nationwide launched their insurance app
  • Samsung Wallet App – exact copy of Passbook

Mobile testing news, updates, tools, training – All in one place – Mobile hub

As a new tester, starting out in the Mobile testing space, I found it really hard to find information about mobile news, updates and the latest developments in mobile. This was driving me crazy and had to consult with many people and do hours of searching for the right information (It was interesting but tiring)

In order to prevent this from happening to anyone else, over the past 1 year or so, I have been making a list of sites I have been referring to, for the above information

So, now any tester who wants to know the latest and greatest in mobile testing can find the majority of the information within the below links (all in one location/blog post).

Mobile testing news, updates and community

Mobile Testing Tools

Mobile Marketing/Usage Statistics

Mobile Blogs

Definitely check out the blogs of my colleagues/friends.They have really good information on mobile testing and in fact I found some of the links based on their suggestions and information they gave me or mentioned on their website.

Responsive Web Design useful information

Also check out my blog post on testing Responsive Websites —

I hope this is helpful to curious and new testers like me :-). I will keep updating this post as and when I come across new resources.

Hit me up in case of any questions.


What do you want to accomplish this year? Setting goals, being a CLOSER!!

I kind of wanted to kickstart this year with a non-technical post relating to a topic which is close to my heart and other people reading this post.

So, firstly, let me ask this, Have you made New Resolutions for 2013?” Or let me phrase it this way “Have you been making New Resolutions as a tradition for the last few years and not kept up any of them?”

Based on what I have seen, the answer to the below question is YES and YES!!!!!

We all make new year resolutions including me and find it hard to keep up with it. For all you know, we start digressing from our goals within a month of the new year. This thought has come to me time and again and for the past few years, I have devised a strategy to cope up with it.

Which is…..

Keep reading inspirational stories, videos, blogs, articles, to remind yourself that, you are an achiever and not a loser. I have followed this for the past couple of years and it has worked for me in my favor. I have been able to achieve at least 75% of my goals (Hey even I am human and I am not 100% perfect in terms of accomplishing my goals.). Achieving a majority of goals is better than not achieving anything at all. At least this is my Motto!!!

I have got inspiration from the resources I have mentioned in the Useful Links section, where I list down the different articles/books/websites which has personally helped me in all facets of life.

It is also worth a mention that just recently, I read this article touching on the same topic and I should say it is the most inspiring source I have ever had to motivate me everyday, to achieve my goals. Believe me, the 5 minutes you spend reading the below article will be the best 5 minutes you have ever spent on something that is of value to you. You will thank me for this, I am NOT KIDDIN!!!!


So today stand in front of the mirror and ask yourself the below questions (it has personally worked for me)-

  • Do you want to be successful?
  • Do you want to stick to your goals?
  • Do you want to be an achiever?

If you have answered YES to the above questions, you have already taken the first major step into SUCCESSVILLE (Yup!!! I patented this word here :-) )

As for me, since I am also human I know I am going to get distracted from my goals but one thing I know is, I will use these resources and above questions, to keep me on track and hopefully I will be an achiever and feel  happy at the end of the year. If not I would have at least tried doing it, which gives me mental satisfaction and a good learning experience.

So, lets go chase our dreams and nothing is impossible if you badly want something.

NOTE: In case you were wondering, I am not turning my blogs into non-technical/non-testing related. Just thought of sharing this with people like me, who want to succeed in this competitive world!!!

I will try to post interesting articles/thoughts throughout this year, mostly testing related.  That is a promise!!!!

Happy New Year Folks!!!!




User Acceptance testing – Highly misunderstood testing jargon/phase!!!!

Me and my team organized our first conference for this year (2012-2013). We started off with a bang.  We brought in Scott Barber (http://www.linkedin.com/in/perftestplus) to start the conference season and it was great. There were about 60- 70 people in attendance and Scott was his usual self engaging the audience right from the start.

He talked about performance testing and other various aspects of testing but one thing which stuck in my head and had a very deep meaning was “User Acceptance Testing”. It was amazing the way Scott barber talked about it and I wanted to reflect some of his and my thoughts on it.

User Acceptance Testing – This simple three word testing jargon has such a deep meaning and is one of the most highly misuderstood testing phases based on my personal experience. Different people have different interpretations of it and have different expectations like-

User Acceptance testing means-

  • Test how the user would see/use the system
  • Once this testing is “Passed/Failed”, we will know how the user would feel about our system. If it “Passes” then it is “ready to ship”.
  • Exercise the most commonly used tasks that the system claims would benefit the user. If these functionalities do not work properly then the product is most probably not going to be used by many people
  • Think like a user and test the system, then you will find most of the issues user would face in real time when the product is released.
  • Give the product to the user acceptance testing team, they are very skilled professionals who think like the user and can find all the defects in the system related to usability.
And much more……………….I can keep going on and on……


The thing people tend to forget or do not realize is, there are millions of people in this world (and based on type of product you are launching some percentage of these millions of people are going to use your product) and it is close to impossible to replicate or think like each one of them. So, what do you really mean when you say “After Usability testing PASSES then we can ship the product”????


Do you have Usability Testing Lab? (Which is far better than JUST having a group of individuals testing the product manually without access to latest technologies related to Usability!!!!)


Do your business sponsors and stakeholders understand that not all usability testing issues can be found in this phase?


Do you realize that you cannot think like each and every individual and about each issue which could affect the user? And there are infinite possibilities of some issue or the other being uncovered by some type of user, using some computer, in some location??


Common guys…..think about it!!!!


The best we can do is,
  • Have a properly equipped Usability testing lab with “eye tracking” (helps to find out which part of the page the user sees the most by tracking user eye movements with sensors) and other relevant technologies
  • Bring in some users with various backgrounds and ask them to use your product in the usability testing lab.
  • Based on the findings try to modify some of the things in the product
  • Before going into production apart from all the other testing you do, finally you do a Smoke test to ensure Critical and most common features which the product claims to benefit the user or the user would exercise in real time are working properly (Can get the recommendation of various stakeholders to identify these modules but the truth is most of the people do not know what they are talking about and it ultimately boils down to the skilled tester testing the product :-) (True story) )
  • And after all the above steps are completed, hope that the user does not uncover any issue that would destroy the products reputation, when it goes into production and pray to whomever/whatever you think gives you that special power!!!!!
As this point of time I can think about only these scenarios.


To summarize, we need to understand what this term really means before just assuming things and using it wildly. If a person thought about the above points I would say, he would to a certain extent understand what are the consequences of misunderstanding this term.


Anyways there are my 2 cents and just my point of view.  If any of you had similar experiences or have something to share hit me up here in the “Comments” section or contact me.  I would love to have a discussion on this and know your perspectives.