Yadda ake saita closed testing track a Play Console, mataki-mataki
An sabunta Nuwamba 2026
Kafin ƙirgar kwana 14 ɗinka ta fara, kana buƙatar closed testing track da aka wallafa, mai testers a haɗe, kuma mai link na opt-in da ke aiki. Yawancin matsalolin da ke zuwa daga baya, kamar testers suna ganin "app not available", suna fitowa ne daga matakin da aka tsallake a nan. Wannan jagora yana bin menus na Play Console na yanzu (Test and release, sannan Testing, sannan Closed testing) da Help Center na Google.
Kafin ka fara
- Asusun developer na Play Console wanda an kammala tabbatar da ainihi.
- Manhajarka da aka ƙirƙira a Play Console, tare da store listing, content rating, target audience, data safety da sauran App content declarations da aka cika. Play Console ba zai bari ka aika release don duba ba idan akwai abubuwan da ake buƙata da suka ɓace.
- Android App Bundle (.aab) da aka sa wa hannu mai package name da kake farin ciki da kiyaye shi har abada. Ba za ka iya canza shi daga baya ba.
- Tsari don testers ɗinka: aƙalla 12, zai fi kyau 15, mutane na gaske masu wayoyin Android da Google Accounts.
1. Buɗe ko ƙirƙiri closed track
- A Play Console, zaɓi manhajarka.
- Je Test and release, sannan Testing, sannan Closed testing.
- Play Console yana ba ka closed track na asali (sau da yawa ana kiransa Alpha). Yi amfani da shi. Za ka iya ƙirƙirar ƙarin closed tracks, amma ɗaya ya isa ga buƙatar.
- Danna Manage track.
2. Zaɓi ƙasashe da yankuna
Buɗe shafin Countries / regions ka ƙara ƙasashen da testers ɗinka ke zaune. Tester a ƙasar da ba ka zaɓa ba ba zai iya sauke manhajar ba.
Google ya lura cewa canje-canje ga ƙasashen rarrabawa suna shafar tracks, kuma ƙarin closed tracks ba sa tallafawa nasu zaɓin ƙasa. Idan testers ɗinka suna warwatse a duniya, zaɓi mafi sauƙi shi ne ƙara kowace ƙasa da za ka iya jigilar manhajar zuwa bisa doka.
3. Ƙara testers: jerin email ko Google Group
Buɗe shafin Testers. Kana da zaɓuɓɓuka biyu, kuma za ka iya amfani da duka biyun a track ɗaya.
- Jerin email: danna Create email list, ba shi suna, sannan ka rubuta adireshi ko ka ɗora CSV. Google yana ba da damar masu amfani har 2,000 a kowane jeri. Ɗora CSV yana maye gurbin adiresoshin da ke cikin wannan jerin. Dole kowane adireshi ya zama Google Account da tester ke amfani da shi a Play Store na wayarsa.
- Google Group: shigar da adireshin group, kamar yourgroup@googlegroups.com. Membobin group ne kawai za su iya shiga gwajinka, kuma dole su shiga group ɗin kafin su yi opt in. Ƙara wani a group shi ne duk abin da kake yi; ba ka sake taɓa Play Console ba.
Idan kana amfani da Tester Exchange, ƙara group testerexchange-testers@googlegroups.com a ƙarƙashin Google Groups ka adana. Wannan adireshi ɗaya yana bari kowane tester da muka aika ya sauke manhajarka. Duba kuma jagorar Google Group da jerin email.
4. Ƙara hanyar ra'ayoyi
A shafin Testers ɗaya, ƙara URL na ra'ayoyi ko adireshin email. Testers suna ganinsa lokacin da suka shiga. Za ka buƙaci taƙaita ra'ayoyin testers a fom ɗin production access, don haka sauƙaƙa: Google Form gajere ko adireshin email na musamman yana aiki.
5. Ƙirƙiri release ka aika don duba
- A closed track, danna Create new release.
- Ɗora .aab ɗinka. Bari Play App Signing ya kula da maɓallinka sai dai idan kana da dalili na akasin haka.
- Ƙara sunan release da gajerun release notes, misali "First closed test build".
- Danna Next, gyara duk kurakurai, sannan Save.
- Je Publishing overview ka aika canje-canjen don duba. Idan managed publishing yana kunne, kana kuma buƙatar danna Publish bayan amincewa.
Ana duba closed test releases a sababbin asusu kafin su fito. Lokaci yana bambanta daga sa'o'i zuwa kwanaki da dama.
6. Raba link na opt-in
Google ya ce link na opt-in yana bayyana ne kawai idan matsayin manhajar Published ne. Kwafe shi daga shafin Testers. Yana kama da https://play.google.com/apps/testing/your.package.name.
A karon farko da ka wallafa, link na iya ɗaukar sa'o'i da dama kafin ya fara aiki. Testers ba za su iya samun closed tests ta bincike a Google Play ba, don haka suna buƙatar wannan link ko link na Play Store zuwa manhajarka.
- Tester ya shiga da Google Account ɗaya da ka ƙara (ko wanda ke cikin Google Group ɗinka).
- Ya buɗe link na opt-in ya taɓa don zama tester.
- Ya sauke manhajarka daga Google Play ta link da ke wannan shafi.
- Ya buɗe ta, kuma ya ci gaba da buɗe ta cikin kwanaki 14.
7. Duba cewa kwanaki 14 suna ƙirgawa
Dashboard ɗinka yana nuna buƙatar closed testing da testers nawa ke opt in. Duba shi kowace rana ko biyu. Idan adadin ya faɗi ƙasa da 12, nemo masu maye gurbi nan take, domin buƙatar tana ƙirga testers 12 da suka ci gaba da opt in ba tare da tsayawa ba.
Yayin gwajin, ɗora aƙalla sabon build ɗaya a track ɗaya. Yana nuna wa Google ka yi aiki bisa ra'ayoyi, kuma testers a track ɗin suna samun sabuntawar kai tsaye.
Tambayoyin da ake yawan yi
Zan iya amfani da internal testing maimakon haka?
A'a. Buƙatar tana son closed test. Google kuma ya ce mutanen da suka yi opt in zuwa internal test ɗinka ba za su iya shiga closed test ba har sai sun bar na internal.
Shin in yi amfani da jerin email ko Google Group?
Google Group ya fi sauƙi idan testers suna zuwa suna tafiya, domin ba ka taɓa gyara track ɗin. Jerin email ya dace da ƙayyadadden rukunin abokai. Za ka iya amfani da duka biyun.
Me yasa ba na ganin link na opt-in?
Yana bayyana ne kawai idan an wallafa release ɗin da ke closed track. Duba Publishing overview don ganin ko akwai duba da ke jira ko canje-canje da ba a aika ba.
Shin tester yana buƙatar Google Account?
Ee. Google ya ce masu amfani suna buƙatar Google Account ko Google Workspace account don shiga gwaji, kuma dole ya zama asusun da ke Play Store na wayarsu.
Zan iya mayar da manhajar closed test ta biya?
Za ka iya, amma Google ya ce dole testers su sayi manhajoji na biya a closed tests. Ajiye manhajar gwajin kyauta don kada ka rasa testers.