Oneguest

oneguest

The 40 Under 40 Fueling Spain's Startup Economy

40 অনূর্ধ্ব 40 স্পেনের স্টার্টআপ অর্থনীতিতে জ্বালানি দিচ্ছে

Die 40 unter 40 treiben Spaniens Startup-Wirtschaft voran

Los 40 menores de 40 que impulsan la economía de las startups en España

Les 40 de moins de 40 ans alimentent l'économie des startups espagnoles

40 अंडर 40 स्पेन की स्टार्टअप अर्थव्यवस्था को बढ़ावा दे रहा है

スペインのスタートアップ経済を支える40歳未満の40人

스페인의 스타트업 경제를 촉진하는 40세 미만 40세

Os 40 abaixo dos 40 impulsionam a economia das startups na Espanha

40 Yaş Altı 40, İspanya'nın Startup Ekonomisini Güçlendiriyor

Nhóm 40 Under 40 thúc đẩy nền kinh tế khởi nghiệp của Tây Ban Nha

40 位 40 岁以下的人士推动了西班牙的创业经济

THE SLOE-WEEVIL

The Ship Dropped Into the Abyss

When starting a podcast, it is normal for a host to want to grow the podcast as much as possible. The desire to grow might lead a host to take actions that are not moral. A host has to keep in mind that taking these shortcuts are short-term solutions. Any misdeeds will either backfire or not help in the long-term. Did you know you can subscribe to the Open Podcast mailing list to get podcasting tips like this directly into the inbox- Click Here to Subscribe Today General Do Not Steal Other People's Content If a host would mention other content from someone else, they should give them credit. To provide them with credit, a host should cite the source of information. The next best course of action would be to put the link to the source in the show notes. Do Not Use Music Without The Owner's Permission If a host were to find a certain song that they like, they should not use it as their intro music. This can cause problems with the creator of the song. There are two courses of action that a host can take to avoid problems. The first action for a host is to use royalty-free music. Royalty-free music is music that is fair use. A host does not have to pay to use a royalty-free song. The second course of action a host can take is to buy a song. There are websites where music makers put songs for sale for a small amount of money. A host can buy a song and avoid any royalty issues with that song. Do Not Inflate Downloads A host should not try to create fake download numbers. Some people claim they can get any podcast on Apple's top 200 list. They will only charge $5 for the service. My mother always says, "if something sounds too good to be true, then it is." This is the case with $5 growth hackers. Their "growth hack" is not a hack at all. They create 30-50 accounts to subscribe to a host's podcast every day. This course of action, for about a week, will get a podcast on the top 200 list. The problem with this technique is that Apple can recognize it as spam. They will remove any podcast from Apple Podcast that creates spam. The quick inflation of downloads is not worth the risk of getting banned from Apple Podcast. Do Not Trick People Into Listening To A Podcast If a host tricks someone into listening to the podcast, they are not a listener of the podcast. That person getting tricked is someone that happened to download a podcast. Relying on tricking people to listen to a podcast makes a host look bad. Decreasing the odds of the person that gets tricked continuing to listen to the podcast. Do Not Spread Fake News Mainstream media outlets try to force their agenda. Stretching the truth for their benefit. A listener does not need to hear fake news from a podcast. The purpose of a podcast is to be a different outlet of information from the mainstream media. Avoid being similar to the mainstream media by checking the sources of information. A host can check the reliability of information by checking with multiple sources. If different sources report the same information, the news is not faked or spun in a certain manner. Interviewing Cut Out Anything A Guest Asks To Get Out In the interviewing chapter, I discussed telling a guest that anything can get edited out. If a guest were to exercise this option, a host should respect their wish. By keeping the unwanted content, a host is burning a bridge. The entire purpose of having guests is to build bridges and build a network. In the future, when a host asks someone to be a guest, that person might reach out to previous guests. If the potential guest reaches out to the guests that had a bad experience, they might not be willing to be a guest. The bad experience of one guest snowballs and impacts the podcast's future. This might lead to a host not being able to find a guest. Which might end the podcast. Survey Do Not Go Overboard Remember that by filling out a survey listeners are taking time out of their own day. A host should not take advantage and ask 50 questions on a survey. The listeners might get annoyed by the action. The types of fans that fill out surveys for podcasts are loyal listeners. If they become annoyed by the host's actions, they may no longer be loyal listeners. Do Not Ask Personal Questions Keep in mind that the survey is for the podcast. A survey should not be to collect information on listeners. Asking personal questions could make a listener uncomfortable. Making a listener feel uncomfortable could lead to losing listeners. Social Media Do Not Spam Not every post on social media needs to be a promotion for the podcast. Someone on social media might discuss a topic related to a host's podcast topic. That does not mean that a host should post a link to their podcast in the comments. That person might have an interest in listening to the podcast. There is no need to inform them about the podcast right away. A host should build a relationship with that person. Interact with them by following and liking their content. For that person to see a host engaging with their content might be enough. When a host engages with the content, that person will see. They will click on the podcast's profile. Which would lead them to the podcast. But if out of context, a host promotes their podcast to that person, that might be off-putting. Which might prevent any type of relationship from growing with that person. Being a spammer may get a host banned on many social media platforms. People do not like spammers. They notice spammers when they click on the profile and see the same comment or post multiple times. Spamming does not help, it does the opposite. A host should want people to view content and by spamming that keeps people away. Some social media platforms consider posting the same comment multiple times spamming. Email Respect The Inbox People get a lot of emails. there is no need to over email subscribers. If subscribers expect an email on a specific day at a particular time, do not abuse that. Stick to the schedule. If people get an email from a host that is off the schedule, they will open it. After days or weeks of getting an unsolicited email, they will unsubscribe and mark the email as spam. Which will hurt the entire email list. Fewer people will be getting the emails, and the email list will be pointless. A host should focus on the quality of the content. By sending out several emails a week, there is no way the quality of each email can be high. The emails, even if they are being opened, are not getting clicks or reads. Doing so only hurts the podcast. Writing Do Not Keyword Stuff Articles Keyword stuffing is the act of adding keywords and places where they do not belong. Keyword stuffing is to increase the SEO score of a blog. A higher SEO score will lead to getting ranked higher in search engine results. Having a higher SEO score means being more likely to come up in search results for search engines. One form of keyword stuffing is adding keywords to a picture's caption. For example, an image of a cat, the caption should be "cat." For someone stuffing in the keywords, might have the caption as "stand-up comedy" or "funny joke." Keyword stuffing is not inclusive. The purpose of captions is for people who use adaptive technology to access the internet. They use a screen-reader, and the software reads the caption of the image for them. If keywords are getting stuffed into the caption, they do not know what the image is. Search engines know this trick. They will lower the ranking of any website that stuffs keywords. Video Mislead People To Watch Videos A host should not use a title that will misrepresent the content in the video. Many video platforms have search tags that a host can use to help people find their videos. A host should not take advantage of and use the most popular tags in hopes of getting the most views. People that feel tricked will downvote the video, and that will lower the video on search results. Meetups Harass People At Events At an event, a host might run into someone that does not want to listen to the podcast. A host should not harass them into accepting a sticker. Harassing a person into accepting a sticker is real-life spamming! Worse, that person that was getting harassed might live in a host's community. A host could run into them at the supermarket or getting their car washed. The worst-case scenario would be that a host runs into the harassed person at another event. That person might talk to other people about the previous event. Leading to those people not talking to a host. Those people might have a bad first impression of a host and not want to listen to a host's podcast. Streaming Do Not Miscategorize Streams As stated in the streaming chapter, platforms have no podcasting category. A host should try to categorize their podcast as close to a platform's categories as possible. A host should not categorize their comedy podcast as a sports video game. The viewers will feel tricked, and they will report any channel that tricks them. The platforms care more about their viewers than the streamers. That will lead to a host getting banned on streaming platforms. Small streamers are not hard to find on streaming platforms. They do not mind kicking them off the platform to make a better experience for the viewers. Podcast to Podcast Promotions Honor Commitment To Podcast To Podcast Partner A host has to build trust with podcast to podcast promotion partners. A host has to trust that their podcast to podcast promotion partner will add their content to the RSS feed. Do not be the person that does not include someone else's episode in the RSS feed. The other host will tell more podcast hosts about their experience. A host will lose the support of similar podcast hosts if they do not honor commitments. Monetization Do Not Lie About Metrics To Advertisers When advertisers approach a podcast host they will ask for download numbers. A host should not lie about their download numbers to an advertiser. Advertisers know the amount of engagement that is possible based on audience size. For example, an advertiser wants a podcast that gets a thousand downloads per episode. If a podcast only gets 100 downloads per episode and they say they have a thousand an episode. An advertiser is expecting 10 to 20 people to use the coupon from the podcast. When only five or six people use the coupon, an advertiser will know the host lied. They will stop advertising as soon as they get the numbers. Once a host reaches 1000 downloads, a different advertiser might reach out. They might contact the previous advertiser for a reference. The previous advertiser will have to tell the new advertiser about the lying. Which could lead to a host losing the new advertising deal. Honor Commitments To Donors Donors give their hard-earned money to a host. The donors have many options for people to give their money to. They choose to give it to a host. When a host says that they will do a certain activity for the donors. They should do it no matter what. If a host says, they will host a Q&A, then make sure the Q&A happens. The donors are paying for these things they are paying for the extra content, a host needs to give it to them. Do Not Cheat People When selling a product, be sure that the product's consumer is getting all the value possible. Do not sell a 5-page eBook for $35. When a host goes to sell a product that equals its value, people will not buy it. They will remember their experience of getting cheated. They will not want to take the risk of getting cheated again. Closing Statement About Ethics And Podcasting In the startup world, there is a belief that every market is a winner-take-all market. The thought process gets peddled by venture capitalists. To prevent competition in the market. Allowing them to squeeze out as much money as possible. For them to maximize their profit from their portfolio companies. There can be several competitors in any industry. In terms of podcasting, that means listeners can listen to more than one podcast of the same topic. One person can listen to multiple podcasts hosted by comedians. There is room for everyone. There is no need to steal listeners away from another podcast. In Terms Of Communities For the Open Podcast Community, there are over a million podcast hosts. Any one of them might join the community. At the same time, there are several podcasting communities. These podcast hosts can join more than one podcasting community. Not every person has to join a host's community. With that in mind, there is no problem for a host to not join or support someone else's community. A host should not join another community to hurt the community. There is no need to steal members away from another community. A host should not sell their community members' data. For a host to use their data to create a better experience for the members has advantages. Making money with a community without selling data is not difficult. There are ads, donations, or creating a product. Selling the members' data is the last option. For a host to sell data, there needs to be a significant amount of data. If a host's community gets to that point and they are not making money, then they suck. Comedians Comedians do not like other comedians that steal jokes. If word gets out that a comedian is a joke thief, that might make it hard for them to get stage time. Which will make it hard for them to grow a following and grow their career. Conclusion Podcasting is a long-term game. If someone is podcasting for a short-term gain, those people are in the wrong business. Some people might want shortcuts to gain an audience. Shortcuts will not work. The shortcuts might get listeners, but they will not lead to subscribers. There is a lot of content out there, and if people do not like a host's actions, they will listen to something else. Being ethical is having a long-term vision. This post is an excerpt from the Open Podcast Community book. Which is available for purchase here . Previously published at https://blog.openpodcast.xyz/ethics-in-podcasting/

Podcasting And Ethical Dilemmas

You have had a great idea, spent some time and are now facing the next questions: How should I approach my building? One of the most used buzzwords in the indie hacker space is “building in public“. It comes in different styles and with different methods. Of course, success in building a side-project publicly also varies. I aim to provide a starting point in this article with a look at methods, platforms, and tools. This blog-post links into the series on introduction in the indie hacker space. validating your business idea What is building a company in public? In the absence of an official description of the term, I would describe it as . The public part can be live as it happens or later, in the form of in-depth blog posts. As with most things, there is no and you have got to choose what works for you and your project. "Any public work on a project aimed to improve, get feedback, build trust and/or attract potential interests" one size fits all The big questions with public building at the moment are: Does building in public still give you an advantage in promoting your side-project or startup? What do you need to get started and what does it take to be successful? What are easy ways of building a company publicly? What options are more for advanced businesses? How is starting a business in public going to look in the future? Why build in public? The idea of building in public isn't entirely new. Many people opt to "build in public" and some good reasons speak for it. If done well, it can drive quite a lot of attention to your project while building up trust in your work. You naturally stay more accountable to your idea and project. Continuously dropped project ideas leave you in a bad light. Also you are building up a brand for your work and work-style. Once people recognize your consistent high-quality work you are building up trust. Same goes the other way: if you are putting together a sloppy solution and present it as a masterpiece people will notice. You will get called out for it. A great example of building a project in public is Ethan's work on . He completely built and designed his email client in public. You can read more on his . Kanban Mail website Methods of building in public The ways to build a bootstrapped business in public vary, naturally. Some are more advanced and time-intensive (live streaming) whereas blogging gives you an easy start and is scalable over time. Blogging about it The earliest versions of were probably the engineering blogs maintained by some bigger companies. With the Internet changing, it's hard to say who started it. Blogging is still a valuable and under-recognized tool. Content marketing, blogging, and guest posts on other blogs are an important part in most marketing strategies. It's building not only an online reputation, but awareness of your project and backlinks. It's also driving transparency and trust. is a very good example of a company maintaining an awesome public company blog and working on the previously mentioned points. building in public Buffer In 2019, WordPress has become quite dated when it comes to blogs. make the tech-side of running your own blog very simple now. An easy starting point for a new blog is, for example, a Netlify-hosted copy of . If you don't have the right domain researched yet, I recommend you check your desired domain names - using my little of course ;) Static Site Generators Hylia Website name checking tool How much time do I need to run a company/startup blog? This is naturally a tricky question to answer. The time demand to run a blog depends on your own expectations and goals. If you drive marketing for your project blog on a daily basis and publish very frequently, this can quickly become time consuming. A solid middle ground might be 1-4 posts per month and shared on social media. This ensures you get some exposure, capture some of the low-hanging SEO fruit and learn marketing basics along the way. One year of consistent blogging with this approach should put you in front of many others, who barely blog or don't use a blog at all. If you want to push it more you can actively work for backlinks. Work towards publishing one guest post on a topic-related blog per month. This requires some time to research suitable blogs, agree on a topic with the lead writer or editor of the blog, and write & edit the article. This is generally an underestimated task but definitely worthwhile. Sharing data and statistics A fairly simple and good way is sharing statistics of your business with the public. Some people are keen to look behind the public facade of a company and look at the business in numbers. is known to study annual reports intensively and draw conclusions from the information. Warren Buffett A new trend in small business is going a similar way by sharing statistics and data widely. No law or public listing requires this for small and medium companies. It's an easy way to gain trust and more chances for businesses to discuss what they do in public. For independent small businesses, this is often done as part of an . If you're unfamiliar with the idea behind this: It's a freely accessible web-page aimed at sharing basic information about a side-project, startup, or small business. Some examples are , or . Previously mentioned, Buffer maintains a complete blog for transparency (linked above). open page Nomadlist's open page Kanban Mail's open page WIP Chat's Open page Live streaming your startup build Live streaming sessions are quite popular. These often contain a mix between coding and talking. Most people talk about their projects, development steps, and reasoning. This being said, there is no need to stream coding sessions only. You could also talk about marketing approaches, writing of emails, invite people and have chats about UX enhancements, etc. The limit is really your creativity and time. How to set up your computer for live stream Tech is getting easier than it was. There are still a few steps included in getting ready. When the 24 hours challenge ran, Pat, Armin, and Melanie prepared a as it's a little more effort getting everything started. handy setup guide for Twitch Where to live stream More and more platforms allow live streaming, including Twitter and Facebook. But live streams for don't seem to stick there. Post-production is often done by uploading the stream on YouTube and adding more meta information around the video. People searching on YouTube won't find you only by the words spoken in the videos. The description is your place to make sure you are found. So don't forget to include a decent description with links to your personal blog and side-project. IndieHackers Don't expect hundreds to follow your live stream from the very beginning. But some people might jump in and see what you are up to. helps to draw some attention to your stream. Shipstreams Maker communities Building in public and maker communities go hand in hand. They're your public forum and support group. Have you got a question? Put it in the chat or post a question on the board. Want to get some feedback? Post it. With every post and question, you are becoming more a member of these communities. The community will support you when you launch your project. As with any community, just coming around to share your links won't get you much love. You should spend some time with other members: talk, discuss issues, and work together on your individual projects. Start with reading, commenting, then ask for feedback and last but not least, present your project. A good general guideline can be found in my . intro article for IndieHackers The most popular communities are and in 2019. Pick one to your liking and go with it. Makerlog WIP.chat Future of building in public Building in public is here to stay. The methods, tools, and platforms will probably change in the coming years, but the concept will remain. Simply because it's building on what is scarce: authenticity and transparency. Building a startup "one tool at the time" A new approach partially related to building in public is the "one tool at the time" idea. I've started doing more little tools and projects. Each of them is solving an independent small problem and gets launched as a separate project under a separate name. I noticed this first with Shopify's business name generator. It's a tool in itself; not part of Shopify's product directly, but it's supporting. And as part of this, it gained a number of backlinks and users being exposed to the Shopify idea and brand. If you are a software engineer yourself, spinning up little tools should come easy, relieving from the "one big project". If you are planning to outsource your development, you should plan ahead and use the partial projects as milestones. One tool at a time is a neat approach for people bootstrapping small businesses, as it splits the risks and work-load naturally into smaller chunks. I see this becoming part of the process for suitable projects in the future. More virtual assistants to facilitate Everyone's time is limited to 24 hours a day. Most people like to sleep, eat and have some time for themselves. This reduces the available work hours. If you are working 9-5 it's even worse. To achieve more, you can either work smarter or hire someone to work with you. For a fair price, you get another 10-40 hours of work and the results from this work. These additional hours are of great use to process videos, proof-read texts, write descriptions, etc. Every step of your work you hand over to someone reliable helps your public building as it frees you to focus on growing your project. You can find good people in the Philippines working from $3/hour upwards. That's only around 500 USD per month for a full-time assistant. Of course, this won't work if you are doing an (almost) zero-budget project. Either way, I see hiring Virtual Assistants (VAs) becoming more and more a thing. It switches you from working in your business to working on your business. Especially if you making the most out of VAs can make the difference. self fund your startup Smarter leveraging of your resources We all have different resources at our disposal. Working smarter means knowing how to use one sort of resource (time, money, education, knowledge, network) to obtain more of another resource. Using a VA is one way to turn money into time but there are others too. If you have time on your hands it's a good idea to learn to code, ask great questions, write content, design or spend time thinking. If you've got money, you should do the opposite. Buy the things that either efficiently save you time or allow you to progress faster. That could be a tool or hiring someone to build, design or write something for you. If you've got a great network, make use of it. Connect people to gain money or favours and build your business from there. Even challenges and problems are a type of resource. Nothing helps with personal growth and coming up with new ideas as do your personal challenges. Make sure you spend the required time validating these ideas before jumping into action. This might sound logical, but it’s not one of the things many people actually live by. For public building this is an important aspect. It shows your followers that you think problems through and find solutions outside of the box. This will make the difference between you and hundreds of other makers who just document their hard work. Got more ideas on where building in public is going? How do you do it? I'm keen to hear what your thoughts on the future of building in public are. What are we going to do differently in the future? Where is building companies in public going? Please reach out via the information on the contact page . Previously published at https://peterthaleikis.com/posts/indie-hackers:-should-i-build-my-side-project-small-business-in-public/ .

Should You Build Your Startup in Public?

Even though we haven’t written any tests yet, Laravel includes the following example tests: /tests/Feature/ExampleTest.php /tests/Unit/ExampleTest.php : I recommend adding an alias for the command above, so you would not need to type each time you want to run the tests P.S. vendor/bin/phpunit For example, I’m using this alias: alias lphpunit="vendor/bin/phpunit" 1/ A guest could see all the articles when visiting /articles Since we are going to test functionalities related to the , let’s first create a class dedicated to this controller. ArticleController php artisan make:test ArticleControllerTest Note that I didn’t pass the flag to the command, which mean we are not creating a unit test but rather a . The newly created class should be located in --unit feature test /tests/Feature/ArticleControllerTest.php You can get rid of the that was included with the . testExample ArticleControllerTest Let’s create our first tests. When executing PHPUnit, it will look for all the public method that either start with or that have in their dockblock. test @test So you could either use this format: public function testGuestCouldSeeListOfArticles(){...} or this one: /*** @test*/public function it_allows_anyone_to_see_list_all_articles(){...} I prefer the second one since it is much easier to read. I’ll start with the most basic test. I just want to make sure whenever I hit the route, I get a valid page back. /articles /*** @test*/public function it_allows_anyone_to_see_list_all_articles(){	$response = $this->get(route('get_all_articles'));	$response->assertSuccessful();} Save the file and run PHPUnit (either using or with the alias we created earlier). vendor/bin/phpunit lphpunit Our tests passed Note that, even though we wrote just one test and one PHPUnit tells us that we have 3 tests and 3 assertions. assertion Note: An assertion is testing one single “thing”, a test could contain multiple assertions . The test we wrote above contains just a single assertion _$response->assertSuccessful();_ The reason behind this, is that PHPUnit will run all the tests in the directory. Running all the tests each time is not a problem at the stage we are in right now, but if you want to run just a single test, you can pass the name of the test (the name of the method) as a parameter to the flag like this: /tests --filter lphpunit --filter=it_allows_anyone_to_see_list_all_articles … and yes, as you might have guessed it you could add an alias for this command in order to save time next time you want to run just a single test. alias lphpunit="vendor/bin/phpunit"  alias lphpunitf="lphpunit --filter=" lphpunitf it_allows_anyone_to_see_list_all_articles As you can tell, we want to test more than just getting a valid page, we want to make sure that we are getting the right page. We can test this with the following steps: make sure that we are getting the right view make sure that the view contains the variables needed for this page Laravel provides two method to test the above: $response->assertViewIs('articles.index');$response->assertViewHas('articles'); Our test class should now look like this: <?phpnamespace Tests\Feature;

use Tests\TestCase;use Illuminate\Foundation\Testing\WithFaker;use Illuminate\Foundation\Testing\RefreshDatabase;

class ArticleControllerTest extends TestCase{	/**	* @test	*/	public function it_allows_anyone_to_see_list_all_article()	{		$response = $this->get(route('get_all_articles'));

		$response->assertSuccessful();		$response->assertViewIs('articles.index');		$response->assertViewHas('articles');	}

} Now that we can test that we are getting the right view (with the right variable), we no longer need to keep the first assertion, since it is implicit. 2/ A guest could see a single article Now that we tested that a guest user could see the list of all articles, let’s make sure that she could view individual articles as well. In order to ensure that this functionality (showing individual articles to guest users) works as expected, we would need the following steps: Get an article to view (randomly) Generate the route to this article and send a request to it GET Make sure that we are getting the right view (in this case ) articles.view Make sure that the view returned contains a variable named $article Make sure that we are getting the article we wanted to access and not another one. Our test should look like this: /*** @test*/public function it_allows_anyone_to_see_individual_articles(){	$article = Article::get()->random();	$response = $this->get(route('view_article', ['id' => $article->id]));		$response->assertViewIs('articles.view');	$response->assertViewHas('article');	$returnedArticle = $response->original->article;	$this->assertEquals($article->id, $returnedArticle->id, "The returned article is different from the one we requested");} Note: We can access the returned view thought the _$response->original_ variable You might ask why we are doing all these steps for a such simple feature. The feature is indeed simple, and its tests are simple as well… simple, but not trivial. We are doing all these steps to insure the following: We want to test accessing a random article each time (we would not want to always request the same ID or the same article), because we might have an issue in the code that makes the application always return the same article. Imagine for instance, that instead of searching for a specific article, for some reason we updated our code to use , we wouldn’t be able to detect this issue if we keep returning the same article (using the same ID) over and over again. Article::first() It is highly recommended to use routes in your tests instead of URLs, because if you ever change the structure of your URL, you wouldn’t need to update your tests. We also want to make sure that we are indeed getting the article we are requesting, because we might get the right view that includes the variable we are looking for, but it might contain a different article from the one we requested. 3/ A guest could see a user profile This one should look a lot like the previous test since the concept is the same (access a model and return it), but we are accessing a user instead of an article. Since we are not testing articles here, we should create a new test class first: php artisan make:test UserControllerTest Then all what we need to do is to add the following test: /** * @test */public function it_allows_anyone_to_see_users_profiles(){    $user = User::get()->random();

    $response = $this->get(route('show_user_profile', ['id' => $user->id]));

    $response->assertViewIs('users.show');    $response->assertViewHas('user');

    $returnedUser = $response->original->user;

    $this->assertEquals($user->id, $returnedUser->id, "The returned user is different from the one we requested");} 4/ A guest could not write a new article and gets redirected to the signup page instead This one (and the remaining ones in this chapter) are much simpler, since they do not require accessing the DB. In order to test this functionality, we need the following steps: attempt to access the route create_new_article test whether we got redirected to the login page [login or signup page ?] The test should look like this: /*** @test*/public function it_prevent_non_logged_in_users_from_creating_new_articles(){	$response = $this->get(route('create_new_article'));	$response->assertRedirect('login');} 5. A guest could visit and get the signup page and 6. A guest could visit and get the login page These two tests are even simpler to write, since we are just checking that when we attempt to visit the login and signup page, we get valid pages. Since we are using the Laravel built-in authentication controller, we would not need to test the authentication ourselves. We would need a new test class for these two tests as well. We could either create a dedicated class just for them. Usually I put all the “page tests” (i.e tests that ensure we are getting valid pages when we hit certain URL) in a (especially if I have a controller named ) ; or just create a test class for since in most cases I add the logic of the pages I tests to this class. PagesControllerTest PagesController HomeController The two test cases should look like this: /*** @test*/public function it_returns_register_page(){	$response = $this->get(route('register'));	$response->assertSuccessful();}

/*** @test*/public function it_returns_login_page(){	$response = $this->get(route('login'));	$response->assertSuccessful();} Also, instead of just checking whether we are getting a valid page (which is more than enough in this situation), we also check that we are getting the right views like this: /*** @test*/public function it_returns_register_page(){	$response = $this->get(route('register'));	$response->assertViewIs('auth.register');}

/*** @test*/public function it_returns_login_page(){	$response = $this->get(route('login'));	$response->assertViewIs('auth.login');} How would tests detect breaking changes in the code base? As we discussed in a previous chapter, one goal for writing tests is to ensure that the functionalities of the application will keep working the way we intended when we first built them. I’d like to show just one quick example of how the tests will inform us that we are introducing a new code that is changing the behavior of the application (a breaking change). Let’s assume that after a few weeks of working on this application we decided for some reason to update the constructor of the from this: ArticleController public function __construct(){	$this->middleware("can:manage,article")->only('edit', 'update', 'delete');	$this->middleware("auth")->only('create');} to this: public function __construct(){$this->middleware("can:manage,article")->only('edit', 'update', 'delete');$this->middleware("auth");} the only change is deleting from the second line of the constructor. ->only('create') This might either happen by accident (a teammate didn’t see the value of protecting just one action with this middleware) or it was done intentionally to prevent guest users from reading articles before signing in. If we run the tests, we would get this: Before writing any tests of the application, chances are that you wouldn’t notice the breaking change before a while. Maybe the breaking change will even get deployed without anyone noticing it, since you’d be using your application as a logged in user most of the time, and you wouldn’t think that you’d need to test the guest functionalities after every small change to the application. But with the tests, any breaking change will be detected right away without even needing to test the application manually. And if you have a CI (Continuous Integration) set up with your project (we will be exploring how to set it up later in this ebook), you wouldn’t even be able to merge/deploy without fixing the issue first. Conclusion In this chapter, we explored the different steps needed to test guest users functionalities. We’ve seen that even though the tests are simple, they sometimes require extra steps to ensure that we are testing the right thing, and we are not missing some edge cases (especially when we introduce a change that might break the application). We’ve also seen how tests would detect breaking changes in the code base. In the upcoming chapters, we will be exploring tests related to logged in users which could be a little more challenging than the tests we’ve seen so far. If you want to follow along, and get notified of any progress with this ebook (new free chapters for instance), please sign up here: https://laraveltesting101.com/

[Laravel Testing 101] Writing tests for guest user functionalities on a Laravel CRUD application

Next.js v15 — What’s new under the hood

Master iOS Multipeer Connectivity and Share Data Across Multiple Devices without Internet Access

মাস্টার iOS মাল্টিপিয়ার কানেক্টিভিটি এবং ইন্টারনেট অ্যাক্সেস ছাড়াই একাধিক ডিভাইসে ডেটা শেয়ার করুন

Meistern Sie die iOS-Multipeer-Konnektivität und teilen Sie Daten über mehrere Geräte hinweg ohne Internetzugang

Domine la conectividad multipeer de iOS y comparta datos entre múltiples dispositivos sin acceso a Internet

Maîtrisez la connectivité multi-homologues iOS et partagez des données sur plusieurs appareils sans accès à Internet

iOS मल्टीपीयर कनेक्टिविटी में महारत हासिल करें और इंटरनेट एक्सेस के बिना कई डिवाइस पर डेटा साझा करें

iOS のマルチピア接続をマスターし、インターネットにアクセスせずに複数のデバイス間でデータを共有する

iOS 멀티피어 연결 마스터하고 인터넷 접속 없이도 여러 기기에서 데이터 공유

Domine a conectividade multipeer do iOS e compartilhe dados entre vários dispositivos sem acesso à Internet

Освойте многоточечное подключение iOS и обменивайтесь данными между несколькими устройствами без доступа в Интернет

İnternet Erişimi Olmadan iOS Çoklu Bağlantısını Ustalaştırın ve Verileri Birden Fazla Cihaz Arasında Paylaşın

Làm chủ kết nối đa cấp iOS và chia sẻ dữ liệu trên nhiều thiết bị mà không cần truy cập Internet

掌握 iOS 多点连接并在无需互联网访问的情况下在多个设备之间共享数据

How to Get Faster Responses With HTTP Streaming: AI For Web Devs

5 Integrations in React: Contentful, Tilda, Hubspot, Typeform, Builder.io

Stories, News & Mentions about ONEGUEST

Oneguest’s Stories on HackerNoon